Monitor resolution messed up, monitor is unknown

Question

im trying to do this:

class Event < ActiveRecord::Base
  belongs_to :previous_event
  has_one :event, :as => :previous_event, :foreign_key => "previous_event_id"
  belongs_to :next_event
  has_one :event, :as => :next_event, :foreign_key => "next_event_id"
end

because i want to enable the user to repeat events and change multiple oncoming events at the same time. what am i doing wrong, or is there another way of doing this? somehow i need to know about the previous and the next event, don't i? when i'm testing this in the consolewith Event.all[1].previous_event, i get the following error:

NameError: uninitialized constant Event::PreviousEvent
    from /Library/Ruby/Gems/1.8/gems/activesupport-2.3.5/lib/active_support/dependencies.rb:105:in `const_missing'
    from /Library/Ruby/Gems/1.8/gems/activerecord-2.3.5/lib/active_record/base.rb:2199:in `compute_type'
    from /Library/Ruby/Gems/1.8/gems/activesupport-2.3.5/lib/active_support/core_ext/kernel/reporting.rb:11:in `silence_warnings'
    from /Library/Ruby/Gems/1.8/gems/activerecord-2.3.5/lib/active_record/base.rb:2195:in `compute_type'
    from /Library/Ruby/Gems/1.8/gems/activerecord-2.3.5/lib/active_record/reflection.rb:156:in `send'
    from /Library/Ruby/Gems/1.8/gems/activerecord-2.3.5/lib/active_record/reflection.rb:156:in `klass'
    from /Library/Ruby/Gems/1.8/gems/activerecord-2.3.5/lib/active_record/associations/belongs_to_association.rb:49:in `find_target'
    from /Library/Ruby/Gems/1.8/gems/activerecord-2.3.5/lib/active_record/associations/association_proxy.rb:239:in `load_target'
    from /Library/Ruby/Gems/1.8/gems/activerecord-2.3.5/lib/active_record/associations/association_proxy.rb:112:in `reload'
    from /Library/Ruby/Gems/1.8/gems/activerecord-2.3.5/lib/active_record/associations.rb:1250:in `previous_event'
    from (irb):2

what is going wrong here? thanks a ton for your help.

Solution 1

The monitor reports its dimensions using EDID. Most probably the monitor does not report correctly the EDID information. In addition, newer X.Org is strict about EDID information.

So, how to figure out if this is an EDID issue;

1. Install the read-edid package with sudo apt-get install read-edid
2. Get the EDID information with sudo get-edid | parse-edid
3. Finally, post the information here (use pastebin).

Solution 2

this is a old question, but maybe I can help someone else with this problem:

I had the same problem, I have the same monitor (acer x193w) and I was not able to set the resolution correct (1440x900). the solution was very simple although I was looking for it for two days. This is the solution: go into the menu of the monitor, select reset and reset your monitor configurations. After this detect your displays again (in the monitor settings or in the nvidea settings) and now my monitor was recognized and I was able to select the correct resolution.

I fount this solution here.

Comments

[Admin]

I've encountered the same problem. Dumped output to pastebin.com/zk8wqb8e

[j-g-faustus]

Had the same problem with an nVidia card and an Acer monitor. Couldn't understand it as it seemed to happen randomly, and in Windows 7 as well as in Ubuntu. Turns out that this happens whenever I boot the computer before I turn on the monitor(!). So at least in my setup, turning on the monitor before I turn on the computer fixed it.

[mickmackusa]

Please edit the question to replace moitor with monitor, cant with can't, and An way with Any way.

[Patrick Oscity]

you're right, i probably won't even need the reference to the previous event. and it works great without the belongs_to! thanks