P: Photoshop creates a gude log while working with files

@Kevin Stohlmeyer  "There are already extensive posts about this bug"

With all due respect, the original issue in this post was resolved back in April/May 2022 with an update 23.3.1 and yes, of course there were extensive posts on it.

However, this same bug has re-appeared in version 24.1 and needs attention. By posting a 'New Post' about a bug in PS v 24.1. I would have thought it would have been easier to catch the attention of someone who could relay the re-occurrence of this bug back to the appropriate Adobe staff.

I started a new thread since this one is cluttered, but it seems someone merged my new thread with this and my account of this bug will surely get lost amongst this.

We shall see. 

Yes, and with no solutions.

I've noticed that when I double click on a PSD to open in Photoshop when the program is closed, Photoshop creates a text "gude-.log" file in that folder. The file is not created when I just go to the PSD file and right click to open in Photoshop.

I've not seen this behaviour until updating to the latest PS version 24.1
I have Windows 10, the latest build.
As usual, I've done all the trouble shooting, as one does when something does not go right with Photoshop. This is more of an annoyance than anything else.

I know it's a bug as this issue had been reported in a previous version of PS at this link here:
gude.log bug 

Admins/Mods, please don't merge this with the other conversation gude.log bug as that particular bug at the time, was fixed with an update 23.3.1. which was back in April/May 2022.

There have since been recent posts (Dec 2022) which needs to be looked into by someone who can touch base with an Adobe Engineer.  I believe this needs a fresh look into, so hopefully by creating a new bug report for Photoshop v 24.1 that this will generate a quicker response by an Adobe Employee. Thank you.

. . . . . . . . . . . . . . . . . . .

Here's what's in the text file

gude-2022-12-30.log

20:48:24:402 [ALWAYS] GUDE Logging Started
20:48:24:403 [INFO] SqliteResumeCache::SqliteResumeCache basedirectory is null/empty
20:48:24:403 [ERROR] SqliteResumeCache::CreateSqliteResumeCache creating resume cache pointer failure
20:48:24:403 [ERROR] Initialize resume cache pointer failure
20:48:24:403 [INFO] gude policy POLICY_USER limit (2,2,1) chunk 2097152, chunking (UL 0 DL 1), resXfer 1, adapt 0, NSURL 0, timeout 86400
20:48:24:403 [INFO] Initialized -- gude-lib version: v0.12.1 app: gude
20:48:26:884 [WARN] Ignoring attempt to reinit logging to \gude at level 4 retaining 3 days of logs
20:48:26:885 [INFO] SqliteResumeCache::SqliteResumeCache basedirectory is null/empty
20:48:26:885 [ERROR] SqliteResumeCache::CreateSqliteResumeCache creating resume cache pointer failure
20:48:26:885 [ERROR] Initialize resume cache pointer failure
20:48:26:885 [INFO] gude policy POLICY_USER limit (4,4,1) chunk 2097152, chunking (UL 0 DL 1), resXfer 1, adapt 0, NSURL 1, timeout 86400
20:48:26:885 [INFO] Initialized -- gude-lib version: v0.12.1 app: gude

. . . . . . . . . . . . . . . . . . .

Opening a file from FE should not produce an error, every other progam I have does not have an issue, and never has in the last 30+ years of computer work.
Someone mentioned Bridge being a best practice - not sure how that is the case as it is really just another FE will lots of bells and whistles - the issue just needs to be fixed on Photoshops side.

Thanks for your note. However, the gude log file is created by Photoshop even when Automatic Proxy Detection is disabled.

Je ne comprends pas cette discution, car sur tout les Windows, certaines erreurs "cachées" 
ont toujours existe juste Adobe crée un log lorsque ce type d'erreur lui ait retourné.
Alors ne demandez pas à Adobe de ne pas nous en informer, (oui c'est inutile) mais cette erreur
existera toujours si vous laissez activé la détection des Proxy en automatique ,
 

You seem to be unaware of programming "Best Practices" ... in Windows there is an Event Log.  Applications can and should create their own entries and registry their own specific application logs with the OS and write their errors to that log.

Alternatively, Adobe can have those errors sent to a server which they can monitor.  Or, Adobe can read their own event log entries and present them via a "useful" end user UI.  But what a software engineer should NEVER do, is create log files next to resource path, that is NOT best practices. 

@Beachcolonist ... a typo warrior ... so your "resonse" I take it means "response" ... the world is officially coming to an end a typo was found ... stop distracting from what you clearly seem unable or unwilling to grasp.

No stomach for getting into the technical details of the errors in these logs?  You seem to want to avoid that discussion entirely?

Anyway, the "real issue" here is that Adobe acknowledged the bug and indicated it would be fixed in next update, it was NOT fixed in the next update (23.x.x) and it was NOT fixed in the new version (24.x.x) and subsequent updates to the new version.

Honestly, you sound like an Adobe employee who is or "was" on the Quality Assurance team and didn't catch this bug ... you're definitely not a PM as you don't know the difference between "solution" and "work around".

I have the same issue, opening a file in Photoshop or Illustrator by double-click in Explorer or just on Desktop creates a gude<...>.log file.
I don't see it as a problem, but it is still annoying.
I wonder why Adobe cannot fix it for months.

As an MS Certified Computer Tech, I would never open any file that is "self" generated or appeared from some unknown source.  You can check the properties by right clicking and often that will tell something about the file.  All that said, the "guide: file continues to appear on my system from time to time.