P: Photoshop creates a gude log while working with files

See:

https://community.adobe.com/t5/photoshop-ecosystem-bugs/solved-unwanted-quot-gude-log-quot-file-creation-issue-in-photoshop-solved/idi-p/13446614

Me and my collegue  have the same problem. Is there a solution for this in the meantime?

gardis - Adobe doesn't jump because a problem is posted to the forum. This trivial bug doesn't even interfere with the operation of the software.

The "staff" here are contributors, volunteers and some employees. We are also supposed to help each other, while Adobe works on the software according to their own corporate rules.

If you review some posted questions at random, you will see that official answers always send people to help pages you could have found yourself Googling the issue, many of which are no help or are circular. Another common tactic is to tell people to reset their preferences. You never get some Adobe engineer answering a post, it would be too expensive.

And for what you do get, you don't "pay big money" for the software, you pay a trival cost for what it does. And it works like magic for endless useful editing purposes. That said, you could find something else if the lack of attention in the forum bothers you that much.

~~~

The way to use the forum is to search for an issue, check to see if a workaround is available, take it and go back to work or play with the software.
Posts about not being paid enough attention to are off topic whining, and they will ignore you. That's how it goes. You have zero authority over Adobe to make demands, believe me, you will find this out in the long run.

If you want to just move forward on this log file nonsense, see my post, "Solved! - Unwanted "gude.log" file creation issue in Photoshop - Solved!"

I'm following this thread with interest and really only have one thing to say.

Where are the Adobe staff? Why doesn't Adobe answer our questions?

We pay big money for the service and are met with nonchalance.

Improvement! Now! 

My comments on the gude*.log issue stand, and are for the benefit of Photoshop users who want to get back to work or play with the software, [removed]. You are free to do as you wish!

Ok, I'll deal with your comments, point by point:

"A workaround only works for the people who are aware of it in the first place."

I am happy to let you know this is not true. A work around works for anyone, anytime, even if they already have numerous log files all over numerous folders.

Really? How can people use a workaround if they're not even aware that one exists? Please tell me. I'm intrigued.

1. They need to be calmed about fears of virus, malware etc. it's not. It's a text file (and you can look at it by opening it notepad with no risk of harm to your PC if you are curious about it).

But regular users just might not even know this. They see files with strange, scary-looking text announcing errors popping up, seemingly by themselves, all over their system. Files that will throw an equally scary-looking error message if they try to open them while Photoshop is still open. Some people just aren't as well versed in computer science as others might be.

2. They need to be told how to remove all the files easily if they want them gone. To do this just search the drive once for gude*.log and delete them all at once.

But they do need to know about this issue before they can take steps to resolve it.

3. They need a workflow to carry on using the software without generating more log files. I detailed three (3) methods in my post titled, "Solved! - Unwanted "gude.log" file creation issue in Photoshop - Solved!"

Ah, so those files are a result of all the people in this thread's own mistake by choosing not to use the correct workflow. Got it.

4. It is not true that, "not-that-advanced, regular users" need a "permanent solution," it's absolutely unnecessary. Making demands of Adobe in this forum is like hollering at a building. You can do it if you wish, but it's not worth the effort.

Here's what's not going to happen if Adobe never learn about bugs in their software: Bugs get fixed.

Did you really call it unnecessary to fix a bug that erroneously creates multiple files on customers' systems? Well, I disagree completely. It's a bug. Bugs get fixed. Especially known bugs, like this one.

5. When you are driving and you come to a roadblock, you take another route, you don't sit and wait for the road to be opened. This is the same thing. Eventually Adobe will fix it.

No, the analogy is more like this: You're driving along like you normally do, and then suddenly error messages start popping up in your dash. Every time you try to drive anywhere, errors galore. And if you try getting help in your car's help forum, you're told you're just using your car incorrectly.

But even after Adobe fixes the issue; using Bridge to review & open and manage and batch process files will be the preferred way to work for serious users, artists, anyone with a lot of files with various types & attibutes. So it's not only a trivial issue, but with intelligent work methods any user, including new users, can prevent it from occurring.

Regular users, as well as serious users and artists, should be allowed and able to use Adobe products however they want without being told they're doing it the wrong way or getting chastised when they try to comment on this issue in a support thread.

Antisoda - You say, "A workaround only works for the people who are aware of it in the first place."

I am happy to let you know this is not true. A work around works for anyone, anytime, even if they already have numerous log files all over numerous folders.

Users need these things:

1. They need to be calmed about fears of virus, malware etc. it's not. It's a text file (and you can look at it by opening it notepad with no risk of harm to your PC if you are curious about it).

2. They need to be told how to remove all the files easily if they want them gone. To do this just search the drive once for gude*.log and delete them all at once.

3. They need a workflow to carry on using the software without generating more log files. I detailed three (3) methods in my post titled, "Solved! - Unwanted "gude.log" file creation issue in Photoshop - Solved!"

4. It is not true that, "not-that-advanced, regular users" need a "permanent solution," it's absolutely unnecessary. Making demands of Adobe in this forum is like hollering at a building. You can do it if you wish, but it's not worth the effort.

5. When you are driving and you come to a roadblock, you take another route, you don't sit and wait for the road to be opened. This is the same thing. Eventually Adobe will fix it.

But even after Adobe fixes  the issue; using Bridge to review & open and manage and batch process files will be the preferred way to work for serious users, artists, anyone with a lot of files with various types & attibutes. So it's not only  a trivial issue, but with intelligent work methods any user, including new users, can prevent it from occurring.

Again, Adobe claimed the problem was fixed, it came back to life, we're letting them know and waiting for a "solution", not a workaround.

So very much this. A workaround only works for the people who are aware of it in the first place. And once you are in the know about this specific issue, you realize it's not really that big of a deal: Just delete the files when they appear or work around it. However, a permanent solution is needed for the not-that-advanced, regular users who suddenly discover these files scattered all over their folders and end up believing there's a serious problem with their system. Hopefully, they will discover this thread and learn about this issue. There do seem to be quite a few new commenters on this thread recently. But by that time, they might've already invested time and energy into scanning for malware, changing settings, reinstalling plugins, software, operating system, etc, etc.

In my personal opinion, Adobe should've prioritized this bug and fixed it permanently a long time ago. Is this opinion really that controversial?

@Beachcolonist You will be on an Island by yourself with the type of attitude you demonstrate here.  I seriously doubt you're in a position to hire anyone or manage anyone ... if you were you'd be spending your days working with HR 24/7 ... within two posts you say "workaround" (which is accurate) to "solution" which is not accurate.

Again, Adobe claimed the problem was fixed, it came back to life, we're letting them know and waiting for a "solution", not a workaround.