[Bug 11238] New: Photoshop CS2 doesn't ask to activate, fails on 2nd run

http://bugs.winehq.org/show_bug.cgi?id=11238

Summary: Photoshop CS2 doesn't ask to activate, fails on 2nd run
           Product: Wine
           Version: 0.9.53.
          Platform: Other
        OS/Version: other
            Status: NEW
          Keywords: download, regression
          Severity: normal
          Priority: P2
         Component: -unknown
        AssignedTo: [e-mail]
        ReportedBy: [e-mail]

Sometime in the last month, Wine stopped being
able to run the Photoshop CS2 tryout properly.
It no longer tries to activate, and on the second
run, it says it cannot continue due to a hardware failure.

The error
err:ntdll:RtlpWaitForCriticalSection section 0x1502750 "?" wait timed out in
thread 004c, blocked by 0009, retrying (60 sec)
pops up on the console during the first run; I wonder if the
thread in charge of activation is deadlocking.

A workaround noted in the appdb is
$ cd ~/.wine/drive_c/windows/profiles/*/"Application
Data/Adobe/Photoshop/9.0/Adobe Photoshop CS2 Settings"
$ rm -rf Adobe\ Photoshop\ CS2\ Prefs.psp

This resets you to pre-first-run state so you can try again,
which could be handy for git bisect, but it's not so great
for end users.

[Bug 11238] Photoshop CS2 doesn't ask to activate, fails on 2nd run

http://bugs.winehq.org/show_bug.cgi?id=11238

--- Comment #1 from Dmitry Timoshkov   2008-01-18 08:07:38 ---
(In reply to comment #0)
> Sometime in the last month, Wine stopped being
> able to run the Photoshop CS2 tryout properly.
> It no longer tries to activate,

My impression was that recent Alexandre's fixes made activation work.
> and on the second
> run, it says it cannot continue due to a hardware failure.

Hardware failure is the bug 9623, isn't it?
> The error
> err:ntdll:RtlpWaitForCriticalSection section 0x1502750 "?" wait timed out in
> thread 004c, blocked by 0009, retrying (60 sec)
> pops up on the console during the first run; I wonder if the
> thread in charge of activation is deadlocking.

Photoshop on startup creates a critical section, enters it, then creates a
thread which tries to enter the same critical section. That looks like some
kind of cleanup technique performed by a thread once main functions leaves
the critical section. Since the critical section remains owned during all
the time Photoshop runs err: above is a side effect of it.
> A workaround noted in the appdb is
> $ cd ~/.wine/drive_c/windows/profiles/*/"Application
> Data/Adobe/Photoshop/9.0/Adobe Photoshop CS2 Settings"
> $ rm -rf Adobe\ Photoshop\ CS2\ Prefs.psp 
> This resets you to pre-first-run state so you can try again,
> which could be handy for git bisect, but it's not so great
> for end users.

Isn't this the same problem as described in the bug 9623, i.e. the lack
of Times.TTF?

[Bug 11238] Photoshop CS2 doesn't ask to activate, fails on 2nd run

http://bugs.winehq.org/show_bug.cgi?id=11238

Dan Kegel  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |DUPLICATE

--- Comment #2 from Dan Kegel   2008-01-18 18:05:42 ---
Yep, this is 9623.  Sorry I forgot about it.

*** This bug has been marked as a duplicate of bug 9623 ***

[Bug 11238] Photoshop CS2 doesn't ask to activate, fails on 2nd run

http://bugs.winehq.org/show_bug.cgi?id=11238

Dmitry Timoshkov  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |CLOSED

--- Comment #3 from Dmitry Timoshkov   2008-06-25 01:39:58 ---
Closing dup.