SnagIt 12 prevents screensaver, auto-lock, display sleep

  • 6
  • Problem
  • Updated 5 years ago
  • Acknowledged
As others have observed, after upgrading to SnagIt 12, my Windows 7 PC and my Windows 8 PC will not engage the screensaver as long as SnagIt is running. This means that my PC will not auto-lock (security issue) when I step away and my dual displays do not turn off (wasting electricity). This is a serious flaw that needs to be addressed promptly. 
Photo of Archer

Archer

  • 5 Posts
  • 2 Reply Likes

Posted 6 years ago

  • 6
Photo of Logan S.

Logan S.

  • 2813 Posts
  • 153 Reply Likes
Hey Archer,

We have seen this, and it will be fixed in the next update. I don't have a timeframe for you on that yet though. The only work around we have right now is to make sure you exit Snagit before you leave your machine. That will enable your screensaver to kick in. Obviously, that isn't ideal, and we hope to have a fix soon. Sorry for the inconvenience!
Photo of Joe Morgan

Joe Morgan

  • 8019 Posts
  • 4341 Reply Likes
Will you also be Merging and Deleting all future Questions AND Responses regarding this issue so that only one question remains along with your response???

It took only 30 minutes to Merge, Bury and Delete this Question and the Posted Responses.

Because if this is going to become a common occurrence. I'd like to know, responding to that question was a Complete Waste of my time.

So, did I just waste some more of my time???

Joe

Photo of Joe Morgan

Joe Morgan

  • 8019 Posts
  • 4341 Reply Likes

To avoid any confusion to my previous response that's posted directly above. This is what the original question evolved into.

Other people that post to these forums might want to know this could happen to them as well.

The way I see it.
To cherry pick questions and answers narrows the scope of having a forum at all. 
What's next. Delete all negative reactions to new updates?

 
Photo of Jason Eagleston

Jason Eagleston, Employee

  • 640 Posts
  • 97 Reply Likes
Hi Joe, 

Just to clarify, the merging question is unrelated to the "auto-lock, display sleep" thread, correct? But rather a general question about how threads are merged/maintained?

Our goal with the feedback community is to allow customers to provide direct feedback to TechSmith as well as build a knowledge base of information for other customers to find answers.

The intent of merging topics is to identify independent threads with the same question/idea and put them in one place so as to make the information easier to find and unify the conversation. By doing this, when multiple customers have the same question, we can provide an answer in one location and future comments or replies can also live in the same place. 

For the example you showed, the two threads were both direct questions about how our maintenance/upgrade/update policy works, we were providing the same information in two places, with two separate conversations happening, we merged those into one conversation, all existing participants/followers of both threads are free to comment or reply to the unified thread. 

I hope this helps answer the question, I'd be happy to chat more about our community and our practices. 

Thanks, 

Jason
Photo of Joe Morgan

Joe Morgan

  • 8019 Posts
  • 4341 Reply Likes
Just to clarify, Correct, this is unrelated to the thread on this page.
But the question I am referring to has disappeared and been deleted completely.
Makes it pretty difficult to respond to that thread.
What I found disturbing in this "merged question" was that the merged question was nonexistent. It merged with the Trash bin maybe.
It was as if the person who posted it didn't exist either.
I fully understand why questions get merged, but the tactic used on this question seems wrong.
Regard, Joe 
Photo of Archer

Archer

  • 5 Posts
  • 2 Reply Likes
Your hijacking of this thread seems wrong -- ironic at the very least.
Photo of Archer

Archer

  • 5 Posts
  • 2 Reply Likes
For anyone else experiencing this problem, it can easily be confirmed by running "powercfg /requests" from a command line. You can, of course, simply exit SnagIt entirely and things return to normal. But for anyone who's been a loyal customer for years and relies on SnagIt as an integral part of their daily workflow, that's a major inconvenience.

I, for one, am disgusted that such a major flaw made it through beta testing (you did beta test, right?) and still hasn't been addressed with an update. This is a potentially serious security vulnerability -- especially for corporate users.
Photo of Tina Cline

Tina Cline

  • 1 Post
  • 1 Reply Like
Just want to add that this is a MAJOR security flaw for machines that need to follow a PCI compliance standard.  It is a shame that this is occurring as the product is used daily by some employees, but they also need to comply with security standards of locking the computer when they step away.  Please fix ASAP!
If they remember to close out SnagIt, then they would remember to lock the computer manually, which they do not since we have to apply the locking policy by GPO.
I hope an update is forthcoming.
Thanks!!
Photo of Bill Collins

Bill Collins

  • 1 Post
  • 0 Reply Likes
Has this been addressed yet? It appears it was from 11 months ago and I am still having the issue.

This conversation is no longer open for comments or replies.