Screen stops redrawing sometimes when moving windows

[Tedesco]

Moving a window, on the bottom of screen there is a zone of 2 or 3 cm you can't pas the window.
The down movement is blocked and the mouse cursor with the closed hand moves down into the inner window area. When you try to move the window ones again upwards you will see a broken graphic part of the window as background and the graphic structure of the window get lost. All these movements with the left mouse bottom pressed.
But:
If you move first the window to the left border and forward out of the screen area you can move the window down without the graphic problem. If at least a small part of the window is outside of the left screen area you can move the window up again passing through the bottom zone of 2 or 3 cm without problems.
On the right-hand side of the screen area these movements are impossible.

A big problem you will have with a windows virtual machine in full screen mode.
You can't use the bottom menu.

(This week y made the upgrade from 16.04.n to 18.04.1 with big graphic problems, black screen etc.
Then reinstall gnome from command line solved the problems with black screen.)

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
Uname: Linux 4.15.0-39-generic x86_64
.tmp.unity_support_test.1:

ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Thu Nov 15 08:07:37 2018
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation 82G33/G31 Express Integrated Graphics Controller [8086:29c2] (rev 0a) (prog-if 00 [VGA controller])
   Subsystem: Dell 82G33/G31 Express Integrated Graphics Controller [1028:0294]
   Subsystem: Dell 82G33/G31 Express Integrated Graphics Controller [1028:0294]
InstallationDate: Installed on 2016-03-17 (972 days ago)
InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
MachineType: Dell Inc. OptiPlex 360
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=es_ES.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-39-generic root=UUID=8a9d54df-bf77-4277-990d-781804a2250b ro recovery nomodeset
Renderer: Software
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/02/2009
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A02
dmi.board.name: 0T656F
dmi.board.vendor: Dell Inc.
dmi.board.version: A02
dmi.chassis.type: 3
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.:bvrA02:bd07/02/2009:svnDellInc.:pnOptiPlex360:pvr:rvnDellInc.:rn0T656F:rvrA02:cvnDellInc.:ct3:cvr:
dmi.product.name: OptiPlex 360
dmi.sys.vendor: Dell Inc.
version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
version.libdrm2: libdrm2 2.4.96+git1811120630.e642f4~oibaf~b
version.libgl1-mesa-dri: libgl1-mesa-dri 19.0~git1811141930.e13dd7~oibaf~b
version.libgl1-mesa-glx: libgl1-mesa-glx 19.0~git1811141930.e13dd7~oibaf~b
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0+git1811071935.5e6fa5~oibaf~b
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git1811140735.746ab3~oibaf~b
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15+git1807201019.ac8f7b~oibaf~b
xserver.bootTime: Wed Nov 14 13:05:37 2018
xserver.configfile: default
xserver.devices:
 input Power Button KEYBOARD, id 6
 input Power Button KEYBOARD, id 7
 input Dell Dell USB Keyboard Hub KEYBOARD, id 8
 input Dell Dell USB Keyboard Hub KEYBOARD, id 9
 input Microsoft Basic Optical Mouse MOUSE, id 10
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:

xserver.version: 2:1.19.6-1ubuntu4.2

[Daniel van Vugt (vanvugt)]

Can you please:

1. Change the bug title to better describe the problem; and

2. Attach a video of the problem.

[Daniel van Vugt (vanvugt)]

Also,

3. You seem to be using an unsupported version of Mesa and other packages. Please remove that PPA (LP-PPA-oibaf-graphics-drivers) from the system and retest.

[Tedesco (tedesco-z)]

Here comes the video.

How can I find that PPA indicated above. With lsmod there is no ...oibaf... on the system.

Could you make a proposal for a better title?

[Daniel van Vugt (vanvugt)]

Thanks!

To remove the PPA:

  1. sudo apt install ppa-purge
  2. sudo ppa-purge -o oibaf # or something like that!?
  3. Reboot

Now tell us if the problem still happens. If it does then please:

  4. dpkg -l > allpackages.txt
     and send us the file 'allpackages.txt'.
  5. sudo apt install mesa-utils
  6. glxinfo > glxinfo.txt
     and send us the file 'glxinfo.txt'.

[Daniel van Vugt (vanvugt)]

Oh, also your kernel is stuck in recovery mode:

  [ 136.650] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.15.0-39-generic root=UUID=8a9d54df-bf77-4277-990d-781804a2250b ro recovery nomodeset

which will cause graphics problems.

To fix that, reboot and then hit Esc as soon as the purple screen appears. Now navigate the menus and choose a regular kernel that does not have the recovery option.

[Tedesco (tedesco-z)]

OK, before working on your to do list .....

Yesterday with an update (Start-Date:2018-11-15 13:49:41) on this linux box there where ...libegl-mesa0... in the list of modules.
There where no indication of restart required but I reboot the system .... and the graphic was frozen.
See picture attached.
There was no possibility to use the mouse or the keyboard to get out of this state.

But with ssh I can connect in.

You will find also the file var_log_apt_history.log where you find the re-installation of the ubuntu-gnome-desktop (Start-Date: 2018-11-14 11:49:00) which results in recover the screen graphic.

[Daniel van Vugt (vanvugt)]

That's a different bug so normally shouldn't be discussed here. However your log shows that the update came from the "oibaf" PPA, which is unsupported and should be removed per comment #5.

Start-Date: 2018-11-15 13:49:41
Commandline: apt upgrade
Upgrade: libgles2-mesa:amd64 (19.0~git1811141930.e13dd7~oibaf~b, 19.0~git1811150730.936751~oibaf~b), libegl-mesa0:amd64 (19.0~git1811141930.e13dd7~oibaf~b, 19.0~git1811150730.936751~oibaf~b), libglapi-mesa:amd64 (19.0~git1811141930.e13dd7~oibaf~b, 19.0~git1811150730.936751~oibaf~b), libxatracker2:amd64 (19.0~git1811141930.e13dd7~oibaf~b, 19.0~git1811150730.936751~oibaf~b), libegl1-mesa:amd64 (19.0~git1811141930.e13dd7~oibaf~b, 19.0~git1811150730.936751~oibaf~b), libgbm1:amd64 (19.0~git1811141930.e13dd7~oibaf~b, 19.0~git1811150730.936751~oibaf~b), libgl1-mesa-dri:amd64 (19.0~git1811141930.e13dd7~oibaf~b, 19.0~git1811150730.936751~oibaf~b), libgl1-mesa-glx:amd64 (19.0~git1811141930.e13dd7~oibaf~b, 19.0~git1811150730.936751~oibaf~b), mesa-vdpau-drivers:amd64 (19.0~git1811141930.e13dd7~oibaf~b, 19.0~git1811150730.936751~oibaf~b), mesa-va-drivers:amd64 (19.0~git1811141930.e13dd7~oibaf~b, 19.0~git1811150730.936751~oibaf~b), libglx-mesa0:amd64 (19.0~git1811141930.e13dd7~oibaf~b, 19.0~git1811150730.936751~oibaf~b)
End-Date: 2018-11-15 13:50:08

That is not an Ubuntu bug. It's a bug in the "oibaf" PPA, just as this bug may also be.

[Tedesco (tedesco-z)]

pgim@PGIMdata:~$ sudo ppa-purge ppa:oibaf/graphics-drivers
.
.
PPA purged successfully
pgim@PGIMdata:~$

then reboot and the same problem see photo

[Daniel van Vugt (vanvugt)]

Next please follow steps 4-5-6 in comment #5, and comment #6.

[Tedesco (tedesco-z)]

And the other points ....
ata:~$ sudo glxinfo > glxinfo.txt
Error: unable to open display

Attached you will find "allpackages.txt"

If it is not possible to recover the display .... and the possibility to analyse the graphic problem according to the title (thanks for the change) I will reinstall this linux box next week from the 18.04.1 LTS ISO.

What kind of information from the box could be useful?
(It was only a upgrade from 16.04.x to 18.04.1 resulting to these problems)

[Daniel van Vugt (vanvugt)]

Before you reinstall, please run:

  dmesg > newdesg.txt

and attach the file 'newdesg.txt' here.

[Tedesco (tedesco-z)]

and comment #6.
If I understood correct .... go to GRUB menu and start with the newest kernel
Advanced options => Ubuntu, with Linux 4.15.0-39-generic

No chance, same situation see photo

[Daniel van Vugt (vanvugt)]

There are no photos attached that you keep mentioning. But it doesn't matter now if you're going to reinstall next week. We can wait and see what happens there.

[Daniel van Vugt (vanvugt)]

Oooh. I see. You most likely will now encounter bug 1727356. Please apply the workaround mentioned in bug 1727356, or try its proposed fix from here:

https://launchpad.net/ubuntu/+source/mutter/3.28.3-2~ubuntu18.04.2

[Tedesco (tedesco-z)]

The photo you found, yes! the link is in #7

I will look your #16

Here you will find the "newdesg.txt" from dmesg ....

[Tedesco (tedesco-z)]

I'm sorry, but I'm not able to follow your proposal from #16, up to now I uses only .deb packages.
Is there a point I have overlooked like an easy procedure.

[Daniel van Vugt (vanvugt)]

I know, it's not well written... Please just try this:

Ctrl+Alt+F4, log in, edit /etc/gdm3/custom.conf and uncomment the line:
  #WaylandEnable=false
Then reboot.

---

If the above is too difficult then download all of these:
  https://launchpad.net/ubuntu/+source/mutter/3.28.3-2~ubuntu18.04.2/+build/15618347/+files/gir1.2-mutter-2_3.28.3-2~ubuntu18.04.2_amd64.deb
  https://launchpad.net/ubuntu/+source/mutter/3.28.3-2~ubuntu18.04.2/+build/15618347/+files/libmutter-2-0_3.28.3-2~ubuntu18.04.2_amd64.deb
  https://launchpad.net/ubuntu/+source/mutter/3.28.3-2~ubuntu18.04.2/+build/15618347/+files/mutter-common_3.28.3-2~ubuntu18.04.2_all.deb
  https://launchpad.net/ubuntu/+source/mutter/3.28.3-2~ubuntu18.04.2/+build/15618347/+files/mutter_3.28.3-2~ubuntu18.04.2_amd64.deb

and then run:
  cd ~/Downloads
  sudo dpkg -i *ubuntu18.04.2*.deb

[Tedesco (tedesco-z)]

OK, I will try it ... Thank you.

[Tedesco (tedesco-z)]

As I mentioned before, I have neither keyboard access nor mouse functions, but I get into this box by a ssh connection from another linux box.
The configuration file looks like:

# GDM configuration storage
#
# See /usr/share/gdm/gdm.schemas for a list of available options.

[daemon]
# Uncoment the line below to force the login screen to use Xorg
WaylandEnable=false

# Enabling automatic login
# AutomaticLoginEnable = true
# AutomaticLogin = user1

# Enabling timed login
# TimedLoginEnable = true
# TimedLogin = user1
# TimedLoginDelay = 10

[security]

[xdmcp]

[chooser]

[debug]
# Uncomment the line below to turn on debugging
# More verbose logs
# Additionally lets the X server dump core if it crashes
#Enable=true

But for the reboot I have to wait to finish a heavy data treatment on this box.
(The 'only' think is the missing display.)

[Daniel van Vugt (vanvugt)]

I don't understand those last two sentences. Can you reword them?

[Tedesco (tedesco-z)]

ok, my situation her at work is, that I have to use this computer, we taking about, for data-treatment.
And as I decided last week to upgrade from version 16.04.x to 18.04.1 I got the display problem.
But fortunately I can still use the computer like a server with my data-treatment inside but without display.

Despite of this experience I confirm I prefer use Ubuntu OS instead of Windows OS.

The data treatment is still running ....

[Tedesco (tedesco-z)]

.... reboot .... SUCCESS!!!

We have back the display and the movement of a window without any problems on left, right and bottom.
But there is a difference to the 16.04 LTS version: Here in 18.04 you can't grab a window in the inner area with help of the Alt-key like in 16.04

OK, but what’s about the background?
I have still desktop and server with ubuntu to upgrade to 18.04.
Do I have to make the same configuration by hand?

Form information:
On Friday I tried to use the source code of mutter-3.28.3 and I got to one status with ./configure.
This doesn’t make a difference with configuration of "WaylandEnable=false"?

.
.
.
.
checking for MUTTER... no
configure: error: Package requirements (
   gl
   egl
   gtk+-3.0 >= 3.19.8
   gio-unix-2.0 >= 2.35.1
   pango >= 1.2.0
   cairo >= 1.10.0
   gsettings-desktop-schemas >= 3.21.4
   json-glib-1.0
   upower-glib >= 0.99.0
   gnome-desktop-3.0
   xcomposite >= 0.2
   xcursor
   xdamage
   xext
   xfixes
   xi >= 1.6.0
   xkbfile
   xkeyboard-config
   xkbcommon >= 0.4.3
   xkbcommon-x11
   xrender
   x11-xcb
   xcb-randr
   xcb-res
) were not met:

No package 'gl' found
No package 'gsettings-desktop-schemas' found
No package 'json-glib-1.0' found
No package 'upower-glib' found
No package 'gnome-desktop-3.0' found
No package 'xkbfile' found
No package 'xkbcommon-x11' found
No package 'xcb-res' found

Consider adjusting the PKG_CONFIG_PATH environment variable if you
installed software in a non-standard prefix.

Alternatively, you may set the environment variables MUTTER_CFLAGS
and MUTTER_LIBS to avoid the need to call pkg-config.
See the pkg-config man page for more details.
pgim@PGIMdata:~/Descargas/mutter-3.28.3$

[Tedesco (tedesco-z)]

I don't know if it's the design or something wrong, with more than 1 virt-viewer window open you can't block the screen.
And the key-combination Alt-L don't block the screen.

[Daniel van Vugt (vanvugt)]

Thanks for your hard work.

We have now established the original bug here was caused by LP-PPA-oibaf-graphics-drivers, so not a bug in Ubuntu itself. That makes this bug report 'Invalid'.

The next problem you encountered is bug 1727356. Only older Intel CPUs (Core2 or older) will have a problem with that. It is now fixed in Ubuntu Updates but the fix won't be included in the ISO until version 18.04.2.

The remaining issues should be discussed in new bug reports. Please remember to keep each bug report about one issue only.

[Tedesco (tedesco-z)]

Daniel, thank you very much, it was a pleasure to help a little bit.