Version 24.0.0.221 intercepts keystrokes as commands rather than allowing data entry.

Report · Feb 21, 2017

Our 10 year old application has suddenly stopped allowing our clients to complete data field entry.

Some characters are treated as hot keys or menu commands amidst entry of names and other form data.

In the last few days 6 clients have reported this flaw. Our only relief so far has been to switch to Chrome with 18.0.0.209.

I anticipate a few hundred more clients will be affected in the next couple days.

Initially Windows 7 Professional with IE 11 was the offender but updating Firefox to 24.0.0.221 gave similar results.

Any advice or guidance would be greatly appreciated.

Report · Feb 21, 2017

Hello, I'm sorry you and your customers have encountered an issue with our new release. If you could, please open a new bug up at https://tracker.adobe.com and provide the following information:

steps to reproduce
detailed descriptions of affected configurations (OS, Browser)
link to affected content

If we can reproduce this problem internally, the chances of us providing a fix (or hopefully a more immediate workaround) go up significantly.

Please let me know the bug number and I'll ask the team to investigate immediately.

Thanks,

Chris

Report · Feb 25, 2017

Tracker

Report · Feb 25, 2017

Things are best described as follows:

BUG #: FP-4198253

4 more reported since my first comment.

Diagnostics to date:

1) All Browsers on all Windows OSs fail in a similar fashion. Typically the space bar behaves as a command or control rather than as a data item when typing into a form.

2) Safari on Macintosh works as it has for 10 years.

3) Chrome with old Flash version (18.0.0.209) Seems to work correctly on Win7 Pro but on start up of app complains about outdated FLASH and selecting update causes puts CHROME in same failing state as IE and Firefox.

Report · Feb 27, 2017

Developer who created the application reported today that it is failing on his Macintosh in the same fashion that it fails on the the Windows OSs.

Report · Feb 27, 2017

Thank you for the bug report. I've reviewed it and it appears we have everything we need. I've escalated this with our engineering managers and we'll have someone look into it ASAP.

Report · Feb 28, 2017

Hi Chris

This was linked to "How To-s" on the using FLASH site.

It's come down to 2 choices I guess.

1) A method to reset a couple thousand PCs and MACs to a working version of FLASH.

2) A way to explain to several hundred clients that the system we built and provided depends on FLASH and is no longer viable.

They'll need to figure out how to deal with maintaining paper records while we try to recover from the surprise.

It took a couple trouble reports and a few days anticipating that end user misuse was the cause for me to get involved.

Dr. Steve who wrote the original app 12 years ago was in disbelief when I finally identified FLASH as the failing component.

A couple of cities with lots of PCs and some large Diocesan cemetery organizations are anxiously awaiting my response to this situation.

People keep right on dying in spite of failed computer systems.

Identifying platform, browser, infrastructure, request for a video, no feed back. What's the plan?

We've got ICONS linking to the ARCHIVE programs on thousands of end user PCs and MACs all of which are failing now with all browsers. Not working since mid February and no clue as to when, how or if it will be fixed.

I'd sure appreciate some response. We have new orders in process we'll have to refund and cancel. Many urgent decisions await a response. I'll be 76 in September. I tell all I'll retire when I'm a customer of one of my customers. If this continues one of them may encourage may assist with my retirement.

Dave Burrowes

937 604-0708 Cell

[personal info removed by Mod]

Report · Feb 28, 2017

Hi Chris

Today your techs saw the problem.

They asked if we had changed our app recently. Not for several years.

They asked if it worked worked with v 23.xx.xx.

We identified that it's working today on a MAC laptop with v 24.0.0.194 but not on Dr. Steve's MAC with v 24.0.0.221.

Sure would like to hear more soon.

Dave Burrowes

937 604-0708 Cell

[please do not post personal info, this info can be viewed by anyone]

Report · Feb 28, 2017

Thank you. I've added your comments to our internal bug report. I'm hoping we have a test build for you to try out shortly.

Report · Mar 02, 2017

Requests from our customers as to when they'll be able to begin using their ARCHIVE data entry and editing program and more complaints are occurring daily.

Report · Mar 03, 2017

Hi Chris

I guess my hopes that ADOBE would be responsive were over optimistic. I've told customers we'd have an answer in a couple days.

I'd like you to visit David's Cemetery — David's Cemetery go to the burial search feature, find Lambdin, Ronald. view the images, data and maps.

David's has been a customer for 30 years there system started with DOS and has an integrated sql interface which use ZOPE and depends on FLASH for what you'll view. It's operated without incident for 12 years but can no longer be updated properly.

David's is one of a 100+ customers we'll have to find a way to repair.

I've identified that the upgrade from .194 to .221 created the change in access. Whether it's something Dr. Steve, Aaron or I can fix on our end is unclear at this point. I'm running an old XPSP3 VMware instance with IE8 not updating and keeping things current for now but 24 days are taking their toll.

I'd appreciate a statement that your not going to address this issue if that's the case. I'm being asked to invest my retirement saving in rewriting in HTML5 to eliminate FLASH.

If I must I will.

I understand that ADOBE states that we use your products at our own risk. That you may change them without concern for the effect on 12 year old applications is clear in your license.

I a great fan of Dr. John Warnock. I taught myself POSTSCRIPT before there were PCs. I had to solve a map printing problem incurred when I was President of the TI Mini Computer User Group many years ago. The David's maps you see on the site still use that same original technology.

Cemetery records in the US go back to the late 1600drds and they expect to have access to them for the next several hundred without starting over when the IT companies cough. I'm determined to provide a smooth migration path for that to occur. I've made it through 40 year and dealt with the changes so far.

Any advice you might offer will be appreciated and considered.

DAVE

Report · Mar 03, 2017

Hi Dave,

From what I understand, this bug should be fixed in our upcoming release scheduled for March 14th. I'm hoping that we're able to push out a public beta next week that also contains this fix. Please keep an eye out for both and do let me know if you continue seeing issues.

Is there a way to be automatically notified when a new Flash Runtime release is made?

Thanks,

Chris

Report · Mar 11, 2017

Is there still some plan for a fix to this problem.

More customers are reporting this failure each day.

Report · Mar 13, 2017

Our release is on track. It should be available globally within the next 12 - 24 hours.

Report · Mar 14, 2017

What can I do to test it here?

Report · Mar 14, 2017

I've got to deal with over 1000 seats using various browsers and OSs from Win311 thru Win10 and MACs.

I'm not sure what instructions I need to provide to insure that all get updated in a timely fashion.

I'd like our guys to try it for day or two before I risk alerting those who haven't yet incurred the failure.

Report · Mar 15, 2017

You can download the latest version from get.adobe.com/flashplayer. The version number of Flash Player having the fix for this issue 25.0.0.127.

Let us know if you face any further issues.

Regards,
Rohit

Report · Mar 15, 2017

Good Morning Chris

I see FLASH v25.0.0.127 on my Win 10 system this morning.

After a dozen restarts and reloads the problem with entering spaces or typing the enter key in the comments area of our records still exists after the first record is entered.

Attempting to enter a 2nd record treats the space bar as an accept and terminates the process as before.

With thousands of records to enter for several new cemetery customers we're at a standstill. Having to exit the browser after each record and restart the process each time isn't an option.

Haven't tried other browsers and OSs yet but with several hundred hours invested already I'm not inclined unless you've got some words of encouragement.

DAVE

Report · Mar 15, 2017

Rohit

Test instance is still active on our server and performs pretty much as described earlier in this discussion. I was preparing my note before I received your reply.

Dave

Report · Mar 15, 2017

An associate addressed the issue for one of our government customers by installing Firefox 51 and your v24.0.0.186 archive copy for one user. He instructed her to ignore and bypass security and FLASH out of date warnings.

So far the system is working as it has for the past 8 years at their site.

Report · Mar 15, 2017

We've got WinXP and Win7 systems with Firefox 51.0 and v24.0.0.186 working today.

Also my Win10 laptop just began to work after I removed the v25.0.0.127 and install v24.0.0.186 this afternoon.