Alexandros Frantzis: 
I made a mistake, mir wasn't running before. With or without your package mir 
wont start, instead I get an X session. However based on the log I got I have 
new info

The log in /var/log/lightdm/unity-system-compositor.log:

ERROR: 
/storage/work/mir.bzr/lp-1217877-possible-fix/src/server/graphics/gbm/real_kms_output.cpp(189):
 Throw in function virtual bool 
mir::graphics::gbm::RealKMSOutput::set_crtc(uint32_t)
Dynamic exception type: 
boost::exception_detail::clone_impl<boost::exception_detail::error_info_injector<std::runtime_error>
 >
std::exception::what: Output LVDS-1 has no associated CRTC to set a framebuffer 
on

 That last line is suspicious for me.

It seems that my laptop can't handle three displays at once. Usually I
plug in two ext monitors, and use them without the internal one. But if
I try to enable the internal while the other two is enabled I get a very
weird error (screenshot is attached, the window was too big, and started
to jump around half-freezing my computer, so I couldn't copy the
contents properly).

Could the cause of this bug be that mir tries to start with both three
displays? I am pretty sure that at least once mir run successfully,
because it caused trouble, so I had to disable it then. Maybe at that
time I started my computer without external monitors? I'm going to see
if mir would run without ext. displays pluggged in.


** Attachment added: "Screenshot from 2013-09-18 10:15:24.png"
   
https://bugs.launchpad.net/unity-system-compositor/+bug/1217877/+attachment/3826634/+files/Screenshot%20from%202013-09-18%2010%3A15%3A24.png

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1217877

Title:
  unity-system-compositor crashes with: Output LVDS-1 has no associated
  CRTC to set a framebuffer on

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1217877/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to