Update from 16.04 to 18.04 and serious screen lagging problems

[Yulay]

I have upgraded from Ubuntu 16.04 to ubuntu 18.04, and the refreshing of the screen in browsers, videos, etc... is really annoying. I would like to solve this problem since this is provoking me constant headache
---
ProblemType: Bug
ApportVersion: 2.20.9-0ubuntu7.4
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/pcmC1D0c: julia 3959 F...m pulseaudio
 /dev/snd/pcmC1D0p: julia 3959 F...m pulseaudio
 /dev/snd/controlC1: julia 3959 F.... pulseaudio
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 18.04
HibernationDevice: RESUME=UUID=3bf717b5-f3c2-45da-9ec8-5926c846f3ea
InstallationDate: Installed on 2014-09-30 (1458 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2)
MachineType: Gigabyte Technology Co., Ltd. H81M-D2V
Package: linux (not installed)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=es_ES.UTF-8
 SHELL=/bin/bash
ProcFB: 0 VESA VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-34-generic root=UUID=34beca2c-8810-4dea-81c4-ea789864bd2f ro nomodeset quiet splash vt.handoff=1
ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18
RelatedPackageVersions:
 linux-restricted-modules-4.15.0-34-generic N/A
 linux-backports-modules-4.15.0-34-generic N/A
 linux-firmware 1.173.1
RfKill:

Tags: bionic
Uname: Linux 4.15.0-34-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 06/25/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: FB
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: H81M-D2V
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrFB:bd06/25/2014:svnGigabyteTechnologyCo.,Ltd.:pnH81M-D2V:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH81M-D2V:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: H81M-D2V
dmi.product.version: To be filled by O.E.M.
dmi.sys.vendor: Gigabyte Technology Co., Ltd.

[Ubuntu Kernel Bot (ubuntu-kernel-bot)]

This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:

apport-collect 1794836

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

[Yulay (yulay2000)]

apport information

[Yulay (yulay2000)]

apport information

[Yulay (yulay2000)]

apport information

[Yulay (yulay2000)]

apport information

[Yulay (yulay2000)]

apport information

[Yulay (yulay2000)]

apport information

[Yulay (yulay2000)]

apport information

[Yulay (yulay2000)]

apport information

[Yulay (yulay2000)]

apport information

[Yulay (yulay2000)]

apport information

[Yulay (yulay2000)]

apport information

[Yulay (yulay2000)]

apport information

[Yulay (yulay2000)]

apport information

[Joseph Salisbury (jsalisbury)]

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.19 kernel[0].

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.19-rc6

[Yulay (yulay2000)]

Still not working and no solution given :-(

[Kai-Heng Feng (kaihengfeng)]

That's because "nomodeset" is in your kernel parameter.

[Yulay (yulay2000)]

It solved the problem!!! Million thanks

Sorry for not having figuring it out by myself, in previous versions of Ubuntu I needed to have it set it that way. Removing nomodeset from the kernel parameter worked. I only made it from grub editor when booting, but I'll introdce the change permanently.