The issue persists when MUTTER_DEBUG_FORCE_KMS_MODE=simple has been
added to /etc/environment. Note that Wayland is enabled; that is,
/etc/gdm3/custom.conf has commented out the line reading
WaylandEnable=false.
It may be relevant to note how the problem does not appear following a
fresh reboot. T
ps - I should have mentioned that the program faults when using an older
version of libSDL2-2.0.so.0.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/2074559
Title:
[nouveau] Top mar
pps - there is also a correlation with locking and unlocking the screen
via OS_Key + L.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/2074559
Title:
[nouveau] Top margin of seconda
The trigger may be when a) the screen is locked, and b) the screen
blacks out. Logging back in after this leads to the flickering black
rectangle at the top of the secondary monitor. This occurs without any
use of SDL.
Switching the monitor off and on does not fix the problem. Disconnecting
and re
Just to be clear, I associate restarting gnome with logging out then
logging in again. Not with unplugging the monitor and reconnecting.
Concerning the present bug report, I'm becoming confident that the
flickering black bar appears at the top of the secondary monitor after
the following steps:
1
ps - I don't know whether this information was preserved in the original
bug report, but it may be important.
First, the secondary monitor is positioned to the left hand side,
relative to the primary monitor. This was set by moving the small icon
of the secondary monitor in Settings>Displays to th
Sorry, you'd asked about that, before.
My secondary monitor shows no signal if the resolution is anything but
the maximum, native resolution of the screen.
Changing the refresh rate may temporarily restore drawing to the full
screen. However, locking the screen and then allowing it to sleep will
The Samsung SyncMaster 2233 does have a menu button that leads to an
information panel which reports:
64.6kHz
60Hz
PN
1680x1050
Alas, 'Adjust for TV' broke everything. I had to Alt + SysRq + REISUB,
and reboot into recovery mode. Remounted the file system for read/write
and removed ~/.config/moni
I wonder whether your observation about refresh rate isn't on the right
track. The drop-down list in Settings > Displays > Samsung Electric
Company 22" > Refresh Rate is as follows (in Hz):
120.00
110.00
100.00
89.94
59.95
59.88
The default setting is for 59.88Hz, where I get clipping. If I ch
Thanks.
I ran this:
for e in /sys/class/drm/*/edid ; do echo -e "\n\n$e" ; edid-decode $e ;
done > edid.txt
So that the path is also copied in. I guess that
/sys/class/drm/card0-DVI-D-1/edid is the interesting one because the DVI
is connected to the offending SyncMaster.
** Attachment added: "e
I logged in with 'Ubuntu on Xorg' selected. There is no artefact when
locking/unlocking the screen, or when changing refresh rates. The list
of refresh rates is shorter, containing only 59.88, 100, 110, & 120Hz;
seemingly in agreement with the edid data.
--
You received this bug notification beca
Please see https://gitlab.gnome.org/GNOME/mutter/-/issues/3619
** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #3619
https://gitlab.gnome.org/GNOME/mutter/-/issues/3619
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mut
12 matches
Mail list logo
