P1.70
04/21/2015
As I was saying before, this only happened since updating to 15.04 from 14.10.
It has more to do with my television not specifying a resolution that is
compatible with modeset. For example, it may say that it's 720p tops instead
of 1280 x 720 but I'm not sure. I do know that
** Changed in: xorg (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1448574
Title:
Have to use nomodeset for install (new problem for new distro)
Public bug reported:
I haven't had this problem since around version 12.04 or before (can't recall
which one precisely) where, during installation, I have to use nomodeset in
order to get my Samsung television to stop turning on and off repeatedly during
modeset problems. I would like to menti
So it hasn't been fixed and it still allows issuing of low-level
commands to monitors which can eventually render them inoperable.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/754284
Title:
Mo
apport information
** Tags added: apport-collected natty ubuntu
** Description changed:
This problem was fixed in 10.10 with an update. While not using nomodeset,
sometime incorrect commands would be sent to the display causing errors such as
entering low-power mode, flickering or simply go
Excuse me, but why have you changed the security vulnerability status to
no when this bug allows direct, unauthorized access to the internal
hardware settings of the monitor enough to literally power it on and off
with commands through HDMI? Direct hardware access by anyone but the
administrator s
6 matches
Mail list logo
