Stop Xscreensaver from locking screen once screensaver starts

Question

I have an app on heroku which scrapes pricing data off a website and saves it periodically. For some reason whenever I run the rake task locally, it acts as expected, but when I run the task on heroku it adds extra output and is saving the object twice for some reason.

Output when I run locally

a,12.80 saved at 2012-10-26 03:36:17 UTC.
b,38.03 saved at 2012-10-26 03:36:24 UTC.
c,22.38 saved at 2012-10-26 03:36:31 UTC.

Output when I run on heroku

a,12.80 saved at 2012-10-26 03:36:17 UTC.
b,38.03 saved at 2012-10-26 03:36:24 UTC.
c,22.38 saved at 2012-10-26 03:36:31 UTC.
#<Stock:0x000000047bb5e8>,12.80 saved at 2012-10-26 03:36:45 UTC.
#<Stock:0x000000047baaf8>,38.03 saved at 2012-10-26 03:36:48 UTC.
#<Stock:0x000000047b00a8>,22.38 saved at 2012-10-26 03:36:52 UTC.

Code

require 'open-uri'
require 'date'

namespace :data do 
  desc "import current blah stock price data to database"
  task :importblah => :environment do

  #pass in a stock and price and save it to the database
  def save_stock(stock, price)
    #store stock data in database
    p = stock.prices.build
    p.price = price
    p.datetime = Time.now.utc.to_datetime

    if p.save
      puts "#{stock.symbol},#{price} saved at #{p.datetime.to_s}."
    else
      puts "#{stock.symbol} didn't save."
    end
  end

  actives = Parent.where("test1 = ?", true)

  actives.each do |m|

    stocks = m.stocks.where('test2 = ?', false)
    stocks.each do |stock|
      if stock.title.start_with?('blah')
        #grab stock price data from blah.com
        url = "blah"+stock.symbol
        doc = Nokogiri::HTML(open(url))
        price = doc.at_css(".value").text[/\d+\.\d+/]
        save_stock(stock, price)
      end


    end
  end


  end
end

I have an almost identical rake task for a different site and it is not saving the pricing data twice. I am using Amazon RDS db if that affects anything.

Solution 1

I think you have to disable the "lock" in two different places. First, open the power manager. You can click on the power icon in the panel and select "preferences" or it should also be in Menu -> Preferences -> Power Manager

De-select "Lock screen...." under the "Extended" menu tab.

Second, open screensaver preferences. Menu -> Preferences -> Screensaver.

Again, de-select "lock screen..." at the bottom of the window.

CREDIT: http://lubuntutips.blogspot.com/2012/06/lubuntu-screensaver-lock.html

Solution 2

I recommend you simply remove xscreensaver by typing sudo apt-get remove xscreensaver This will solve your problem, if you don't need a screensaver, your screen still turns black by your energy safe settings.

Solution 3

On a fresh Lubuntu 18.10 install, I went to Preferences > LXQt settings > Session settings and unchecked Lock screen before suspending/hibernating and that seems to have done the trick.

Solution 4

For default setup of Lubuntu 14.04, the locking can be disabled via Preferences -> Light Locker Settings. In my case, "Automatically lock the session" was "Never", yet the session was still being locked after around 10 mins of inactivity. So I turned "OFF" the "Enable light-locker" setting, which did the thing for me. I also disabled all "locks" in Power Management as in @algebralives's answer. Don't know if it was required, but definitely not sufficient.

Solution 5

Spent days trying to fix this, looked at loads of solutions, and then finally found how to fix it. I have an install of LXLE, and after switching every screensaver setting off still got the locked screen after exactly 10 minutes...

Simply go into Synaptic and uninstall "xautolock", then reboot... problem solved for me!

View more solutions

Comments

[Kendrick]

Granted most screensavers dont do what they need to. moire2 is a good example of ones that do work. screen burn in is still a problem even on lcd's I have a pc that the right monitor is rotated and has a scroll bar on the right side of the screen about 12-16 hrs a day. I set the screen saver for 10 min and blank for 20 so that moire can excersize out that scroll bar burn in. after about 3 months of use like that you could easily see where the scroll bar and other buttons were due to burn in.