Photoshop CC undo bug with shapes

I'm wondering if anyone else has experienced this problem. I'm using Photoshop CC on a PC and when I change the color of a shape if I ctrl+z to undo, it often (but not always) gives me this message the first time
and then crashes if I try to ctrl+z again giving me this error
For the most part I've gotten pretty good at remembering never to try and undo a shape color but sometimes your fingers hit those keys so quick that it gets annoying to have the goofy program crashing on you.
One thing to note is it works fine when you first make the shape, I can undo/redo no problem. It's when I go back to edit a shape that this problem occurs.

Hi,
Glad you were able to get the update. That is a Win only issue in 15.0.0 that we fixed and updated in 15.1.0.
regards,
steve

Similar Messages

Photoshop Elements 11 bug with Yosemite not with Maverick

Dear all,
Since I upgraded my OS from Maverick to Yosemite on my Macbook Air, I have a new bug in Photoshop Elements 11 : when I move an element and release the left click, the element return to its initial position. It's very frustrating.
Steps to Reproduce:
1. Create a new element text
2. Move it with the left click to another place
3. Release the left click
Expected Results:
I expected that the element stays in the new position.
Actual Results:
The element return to its initial position. So the move doesn't work.
I can only move the element with the arrows of the keyboard but that's not the best way.
Thank you for your help on this,

Hi,
Are you using track pad for this operation?
If yes, please use mouse instead and see if your issue is resolved.
Thanks!!

Photoshop 2014.2 bug with duplicating layers in different doc

Encountered an issue with Photoshop 2014.2 that occurs when I try to use some_basic_bitmap_layer.duplicate(some_layer_in_different_doc, ElementPlacement.PLACEAFTER). So this is code that has been pretty much unchanged for a year and works in CS6 and CC2012 and used to worked in CC2014.1. I use .duplicate() with docs and with layers inside same doc, but this is the one giving exception:
General Photoshop error occured. This functionality may not be available in this version of Photoshop.
- The object " <unknown> of layer 2" is not currently available
Another strange thing is is that in ESTK debugging the exception surfaced in a bit different places depending on factoring. I.e. before I added more detailed exception catching, it occured later in code. But this place is the only spot there is a layer named "layer 2". But gives me the feeling it's an internal state corruption
I'm guessing it might so specific no-one else will hit it, but I'd like to ask
- Any workarounds you can think of?
- Any ways to directly escalate it to Adobe given it's a new release. The general feedback site seems a waste of effort.
- Any way to downgrade (in a way that normal users could do it also) to 2014.1?

Thanks for the feedback!
The sample code is meant for the sample psd, so it's playing on assumption that there is only one layer that is not background, is visible and not locked. In the production code it's always inside a group so it's not a background and we check for locked. Visibility we don't check but it has not been the case in the PSDs we've replicated this in.
However playing with this I did manage to find a workaround: it's possible to duplicate the layer to beginning of doc and then move it like below.
try {
    var original_doc = app.activeDocument
    var copy_doc = original_doc.duplicate("copy_doc", false) // duplicate original
    var export_doc = app.documents.add(original_doc.width, original_doc.height, original_doc.resolution, "export_doc", NewDocumentMode.RGB, DocumentFill.TRANSPARENT) // create empty export doc
    app.activeDocument = copy_doc   // select copy and first layer of it
    var layer = copy_doc.artLayers[0]
    // create dummy layer to merge to to flatten all vector & style data
    var tmp_layer = copy_doc.artLayers.add()
    tmp_layer.move(layer, ElementPlacement.PLACEAFTER)
    layer = layer.merge()
    var duplicate = layer.duplicate (export_doc , ElementPlacement.PLACEATBEGINNING)
    app.activeDocument = export_doc
    var dummy = export_doc.artLayers.add()
    var target = export_doc.artLayers.add()
    duplicate.move(target, ElementPlacement.PLACEAFTER)
} catch (e) {
    alert(e.message)
} finally {
    copy_doc.close(SaveOptions.DONOTSAVECHANGES)
    export_doc.close(SaveOptions.DONOTSAVECHANGES)
Also if I try to move duplicated layer without setting the active document Photoshop raises the same exception "The object " <unknown> of layer 2" is not currently available". I.e. it's hitting some internal issue instead of giving the right error of "not allowed to move layers in non-selected document". It kind of makes sense, i.e. duplicating to different doc after certain layer is a combo operation that duplicates to different doc and moves and they different requirements (what is the active doc).

Bug with selection tool in Photoshop CS

Hi there,
I find a bug with photoshop.
I work on video editing, so I usually create some image with not square pixel. In DV for exemple, we use 1,066 pixel ratio.
So I create a layer in full screen for DV editing (720*576 pixels for PAL in Europe) with 1,066 pixel ratio.
If I want to delete a area with 720*576 ratio, I use the selection tool and I select (keep the ratio 720*576) ... but the area wich I delete Is not really the correct ratio 720*576 !! Because, If I create a layer with the object tool (create a rectangle) with the correct ratio 720*576, It isn't the same shape as my old area.
So I think there is a bug ... isn't it ?
PS : sorry for my english, but I'm french.

I have test this problem with a friend on a CS3 version.
There is the same problem !
But we don't have the CS4 ... anybody want to test this ?

Bug with big Black Pixel on Photoshop CC

Hi,
I recently install Photoshop CC (iMac 2,8 Ghz Intel Core i5, 16Go 1333 Mhz DDR33, Mavericks)
When using different layers, I have a HUGE BLACK PIXEL coming on the picture (365x365px) , often on the low lef corner.
It disapears when I strongly zoom inside but it comes back when I zoom out...
Any idea please ????

Many thx Mylenium,
it seems to be working right now without OpenCL... I also had a bug with zoom in and zoom out but it seems to be ok too...
I hope it will continue..
(I use to work on heavy pictures with many layers, hope everything will not be too slow without OpenCL)

Photoshop CS4 Trial Bugs - Eraser & Text problems

Hows everybody doing...I recently downloaded the Photoshop CS4 Extended Trial and installed it on my computer...I am noticing some bugs and im not really sure if its just a bug in the trial version which will be fixed when i buy the program or if there was an error with the install...
I dont have screenshots at the moment since im not on the computer having the issue but i can get them if needed...
First lets start with the eraser tool...When i set the eraser tool as a size of say about 10px it works fine...However, if i zoom in on the image above its nautral size i start to lose the eraser...When i say lose the eraser i mean you can no longer seen the round area which will be erased..When you zoom in part of the circle disappears...It will still erase and area of the set size but its sort of hard to do erasing on detailed images when you cant see the whole eraser....
More bugs with the eraser....If i set the eraser to a larger size, say 30px or more, i right off the bat start seeing less of the eraser area....It will go from a whole circle down to something like a half moon with only half the circle being displayed...
This may be a little hard to understand so if need be i will get some screenshots of what im talking about later....
I am also having a problem with the text...For starters, i cant scroll through the text...When i enter text and highlight it and highlight the fonts i would expect to be able to scroll through the fonts while watching the actual text change on thet screen....I am unable to do that, i highlight the text and the fonts and CS4 will let me scroll maybe 4-5 fonts and then it just stops and wont scroll anymore...
Another issue im having with the font is the size....Whenever i enter text it is extremely small...Even if im working with a 200px x 200px image if i set my font at say 75px its tiny, tiny enough to where i cant even see it to highlight it....There appears to be something wrong with the sizing of the text...Just to get text to show up normally, at a readable size, i have to set the font size to 800px+ and this is on images which are only like 600px wide and 300px tall...Usually a font of 800px would fill up this image but when i do it the 800px font shows up like a 36px font...
Like i said if this is all to hard to understand i can get some screen shots later on...I wanna make sure this is something which can be fixed before i go ahead and drop 700+ on the program...

Yes i installed the patch...That was the first thing i did, before checking the video driver...The patch didnt fix any of the problems im having...The video driver update did however fix the eraser/brush issue...
I did what you said in post #1 about un-checking the option listed....When i did that nothing changed for me....
I have some more details about the scrolling issue though....From what i am able to find it seems that if i just enter digits i am able to scroll through the entire list of fonts and see a live preview of every single one....
With any sort of text it will only allow me to scroll through 5-6 fonts...You can see that it wants to scroll more when i hold the arrow down cause you can see the blue hightlight flashing and the words trying to change but it just wont go any further...At times when i hold the arrow down to scroll through the fonts it will scroll through 5-6 and then all of a sudden just go white and wont let me scroll up or not...At that point i have to select the font list and pick a font

How do you turn off the auto select behavior when working with shape layers?

How do you turn off the auto select behavior when working with shape layers?
I am using either of the path selection tools to select only some of the paths on the layer. I have the proper layer targeted. I have the selection too auto select option turned off.
If another layer has a path in that area, that layer becomes auto targeted and I get the wrong path. Turning off the layer is the only way to avoid this but then I have to turn on the layer back on between making my selection and transforming to use the other layer as guide. Is there any way to stop this auto select? Locking the other layer does not stop the auto select, just prevents editing.

As far as i know the move tool options don't have any effect on the path selection tools.
You might try clicking on one of the path points or on the path itself with one of path selection tools and if you want to select multiple points
you can shift click with the Direct Selection Tool or Alt click to select the entire path.
more path shortcuts:
http://help.adobe.com/en_US/photoshop/cs/using/WSDA7A5830-33A2-4fde-AD86-AD9873DF9FB7a.htm l
http://help.adobe.com/en_US/photoshop/cs/using/WSfd1234e1c4b69f30ea53e41001031ab64-7391a.h tml

Adobe Photoshop Elements 11 compatability with windows 8?

Hi, Can I install Adobe Photoshop Elements 11 and Premiere elements 11 if I have windows 8? i.e. is Adobe Photoshop Elements 11 compatabile with windows 8?

PSE 11 and Windows 8 and/or Outlook 2013 have several reported bugs. For example Outlook 2013 and PSE 11 are incompatible because all features (for example Photomail) do not work. Adobe will not support Outlook for email. The user community is unsure of whether it is an Outlook or Windows compatibility problem - but it something!

Photoshop CS5 not working with Lucida Grande Regular font

On my iMac Intel Core 2 Duo 2.66 GHz, I am running OS 10.6.7.
When using Photoshop CS5, if I try to use the font, Lucida Grande Regular, it causes an error.
"Could not use the type tool because of a program error."
When I try to open an existing file that has type layers that include the font Lucida Grande Regular, Photoshop will not open the file. I have several of these files that I want to use. I can open them on another Macintosh and everything works fine.
First I get a message window that says, " Some text layers might need to be updated before they can be used for vector based output. Do you want to update these layers now?" I click on update and then get the following message. "Could not complete your request because of a program error."
I have updated Photoshop CS5 to the latest version, 12.0.4.
I have run the FontTest.jsx script and it shows an error for Lucida Grande Regular.
(IOError: General Photoshop error occurred. This functionality may not be available in this version of Photoshop.
- <no additional information available>)
The other 100+ fonts on my machine did not create errors.
Since Lucida Grande Regular is an essential font for Mac OS X, I re-installed OS 10.6 in order to have a new version of Lucida Grande Regular. After that re-install I am having the same problems with the font not working in Photoshop.
It also does not work with Adobe InDesign CS5. The font does work in Microsoft Word.
The program Font Book verifies Lucida Grande Regular.
Other fonts including, Lucida Grande Bold, work fine in Photoshop and InDesign.
What can I do to get Photoshop CS5 to work with Lucida Grande Regular?

Wow, I'm so glad I found this thread. This problem has been dogging me for years, and it's so sporadic that I've been afraid of breathing the wrong way lest I somehow incur that diabolical Program Error dialog. I'd managed to reach a truce with Photoshop CS5, getting it into a barely working state, and avoiding all updates... until Lion came along today. Then I updated to CS5 12.0.4, and the Program Errors were back again.
Now I see that the problem does seem to be related to the Lucida Grande font. If there's a layer with that font in it, not only can I not edit that text, but I can't marquee select anything, nor drag any shapes. Deleting caches and massaging fonts are completely ineffectual measures... but if I delete the Lucida layers entirely, we're back in business.
At least so far.
Funny to think that of all the innovations I'd like to see Photoshop adopt, the fixing of this one issue is the thing I'd like to see most. I'll be keeping my eye on this thread, and any updates by Mr. Cox.

Is adobe photoshop elements 11 compatiable with windows 8

Is photoshop elements 11 working with windows 8?

PSE 11 and Windows 8 and/or Outlook 2013 have several reported bugs. For example Outlook 2013 and PSE 11 are incompatible because all features (for example Photomail) do not work. Adobe will not support Outlook for email. The user community is unsure of whether it is an Outlook or Windows compatibility problem - but it something!

InDesign bug with wacom intuos

Hello! I have a problem with In design. Since I got a new wacom intuos pen and touch, I have a bug with In Design, it won't save or save as, can't even do UNDO. Does anybody has ever experience this kind of problem? I have mac OS X version 10.6.8 and Adobe CS5.
Thank you!

Yes. But working in CS6. Can't save. Wacom stylus doesn't respond until I tap somewhere out of the CS6 environment and then tap back in the CS6 environment. Then sometimes stylus responds. Also try edit/purge/all action. It seems to help, but in reality this is no way to work.

Undo bug, mouse pointer disappears?

Is just me or everyone has that annoying "undo" bug?
That's what happens: when I press UNDO speedgrade starts to behave strangely.
- If I press undo after clicking right mouse button (and I'm moving a color wheel with mouse) comes out a message "optimizing timeline" and timeline thumbnails are shown under the timeline. Sometimes there is a worst scenario: mouse pointer disappears and I have to quit SG and reopen to get my pointer back.
- Pressing ctrl-z without right mouse button clicked (outside wheel edit mode, or whatever it is called..) sometimes works, sometimes appears the annoying progress bar "optimizing timeline" and several steps of undo are taken, even if I pressed cmd+z just one time.
I use undo A LOT, and now I'm not confident using it because of this strange behavior (I'm on osx).
Are you experiencing the same problems?

You won't believe this but just cleaning a mouse can improve performance... read the following:
How to Clean a Mechanical Mouse
This article explains when and how you should clean a mechanical mouse. It does not apply to the the Apple Pro Mouse.
You should clean a mouse if it is does not track smoothly, or if it jumps or skips. A mouse contains a small ball that must roll smoothly for the mouse to work properly. You should keep this ball free of dirt and oil by using the mouse on a clean, lint-free surface, and cleaning it occasionally.
Use the following procedure to clean a mouse:
1. Turn off your computer.
2. Turn the mouse upside down and rotate the plastic ring on the bottom counterclockwise to release it.
3. Turn the mouse right side up with one hand and catch the ring and ball with your other hand.
4. Clean the three small rollers inside the mouse with a cotton swab moistened with water. Rotate the rollers to clean all around them. If there is a build-up of material on the rollers that the cotton swab does not remove, you can use your fingernail to gently remove the material.
5. Wash the mouse ball in soapy, warm water with a mild soap such as a dishwashing liquid if oil from your hands has collected on it. Be sure to dry the mouse ball thoroughly.
6. Gently blow into the mouse case to remove any accumulated dust.
7. Put the mouse ball back in the mouse case and replace the retaining ring.
If cleaning the mouse as described does not correct your issue, the mouse may need to be replaced. Have an Apple Authorized Service Provider check it for excessive wear or other failure.
If that doesn't do the trick, if this is a mouse that required 3rd party drivers, you might try reinstalling the drivers. Also, try going back to default Mouse preferences on all Users, see if makes a difference.
Carolyn

[LR 4.1 - Library] Minor but annoying bug with mouse cursor

Hi,
There is a minor but irritating bug with the mouse cursor in the Library module. Steps to reproduce:
1. Activate the Library module.
2. Move the mouse cursor into the image area. The mouse cursor looks like a magnifying glass.
3. Move the mouse cursor to the left, until it reaches the right border of the left panel. The cursor becomes a double arrow indicating that you can modify the left panel width.
4. Do not click and continue moving the cursor to the left : most of the time (but not always) the mouse cursor is not reset to a standard cursor when entering the left panel area. It is still displayed as a double arrow.
5. Sometimes this also occurs when moving the mouse cursor directly from the image area to the left panel.
This can also happen under other circumstances. However, this doesn't happen with the right panel or when using another module. Also, at some time during the session, the problem disappears... until the next session or until you return from another module.

I agree, although it sounds trivial, it is very irratating - especially when doing a lot of keywording.
You could add your vote to a previously raised bug report on this ...
http://feedback.photoshop.com/photoshop_family/topics/lightroom_4_library_module_keyword_l ist_cursor_problem
Alan.

Is Adobe planning on fixing any of the LION bugs with CS5?

I've been reading a lot about these bugs with Adobe CS5 applications and LION (here's some> http://kb2.adobe.com/cps/905/cpsid_90508.html). A friend had a ton of problems and ended up sending her laptop back because of them (she wasnt able to downgrade to Snow Leopard over Lion with that particular laptop). I just ordered a new imac, and think I'm going to be using my old one for a while if there are all these bugs. I primarily use my mac for Photoshop, Illustrator and InDesign, and if they are going to be problematic that is going to be a big drawback for me. I talked to an employee at Apple this weekend, and he said Adobe is always behind the ball with getting their software up to speed with new operating systems. Which didnt make me feel anybetter. Lion's been out for a while now, and I assume Adobe received the OS way before it was released to the public in order for them to upgrade their apps to make them compatible. Does anyone know what the status is on when the next big Adobe update is going to happen to address these issues?

As to bug fixes, you'd have to ask Adobe that question. I would presume they'll fix at least some of the issues before the next major release, but what specifically they'll do, only Adobe could tell you. Note, though, that most of the issues Adobe publicly acknowledges are pretty minor and/or are present in earlier versions of the CS suite, not 5.5.
Regards.

FURIOUS! Warning: Undo Bug and Auto-Save Bug

So I'm pretty ticked off right now. I generally liked FCPX and its changes contrary to many others' opinions, but I just came across a bug that ultimately was worse than I thought.
During my editing process, at some point I was unable to undo changes. It was greyed out in the toolbar, and Command+Z wasn't working. It was annoying, but I didn't think much of it or bother to restart FCPX because I was in the zone and didn't want to stop. Eventually, I decided to restart FCPX to see if I could fix the bug with a lull in my edits. It closed out as normal.
When I re-opened FCPX, I found out that my project was at an EARLIER state. From what I can guess, when the undo bug happened. So, during that period of time, NOTHING was being saved. Since you CANNOT auto-save (I know you can duplicate a project, but Im not interested in that, I just want to save a copy manually), there is no way I can recover my edits. I lost about an hour or so worth of edits. Since FCPX doesn't support "versions" yet either, there is no way I can retrieve it.
I do not know if this is a bug due to 10.7, nor do I really care. I sent a bug report because this needs to get fixed. I consider you do the same but AT THE VERY LEAST, be mindful of this bug. If you suddenly can't start undoing, either STOP IMMEDIATELY or duplicate your project (maybe that would work). I'd hate to have someone else go through this problem too.
Sorry if this message is written poorly, like I said, I'm pretty ****** that this key function (Apple's ONLY way to save) failed.

Thanks guys for the tips. Unfortunately though stuck, I don't know if the finder trick will work. Remember, I never really had the file LOST, the changes were simply not writing to the actual .fcp file. So if I copied it in Finder, I think it would just copy the .fcp file which is currently not getting saved to anyway. Maybe duplicating the project in FCPX would work, but again I think that just takes the .fcp file and duplicates it. If it's not writing to it, then its a moot point. Oh well.
As with anything that frustrates anyone, I've cooled off haha, and doing the re-edits actually seemed to turn out easier and better then second time (you know, as theu naturally are I suppose haha). Obviously all sorts of problems happen with technology, its just a shame that its a bug that revolves around the ONLY save feature haha.
HOWEVER. I think I have replicated the problem, and MIGHT know the source of it. Or at least one. If someone wants to try this and confirm this? I'm running OSX 10.7 and FCPX 10.0 (obviously), however I encourage someone with 10.6 to try it too.
I noticed the "undo bug" (and thus the auto-save bug) happens when I took one of the "fader handles" (I don't know the actual name, but its the little marker-like icon found at the start and end of audio tracks, which when dragged, let you easily make a fade in or out. If you take a fader-handle, an drag it ALL the way BEYOND the length of the clip, it should get stuck. Youll notice you cant easily make a change to it again, and you can't undo it. I think this is what causes the problem, as I think this happened twice to me.
If this is it, I hope I can find a way to flag this for Apple so it can get fixed! At the very least we can be concious of it.

Photoshop CC undo bug with shapes

Similar Messages

Maybe you are looking for