Problem with DRI2 and GLX - bionic 18.04
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
mesa (Ubuntu) |
Invalid
|
Undecided
|
Unassigned |
Bug Description
I have encountered the problem described below, after some recent updates in my Kubuntu. After asking on "Answers" I was requested to open a bug, so I'm doing it.
My problem was, that kwin stopped to show graphical effects. I'm using a laptop with Intel graphics - HD5500
After some log file search I've found, that probably the cause is shown in Xorg.0.log:
Xorg.0.log:[ 7073.803] (II) AIGLX: Screen 0 is not DRI2 capable
Xorg.0.log:[ 7073.803] (EE) AIGLX: reverting to software rendering
After some googling, I have found article below, explaining possible root cause. I have used a solution proposed there, and after installing libegl-
Link below describes details:
https:/
Here is some output from my OS diag tools:
lshw -C display
*-display
description: VGA compatible controller
product: HD Graphics 5500
vendor: Intel Corporation
physical id: 2
bus info: pci@0000:00:02.0
version: 09
width: 64 bits
clock: 33MHz
resources: irq:47 memory:
lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu Bionic Beaver (development branch)
Release: 18.04
Codename: bionic
uname -a
Linux hostname 4.15.0-10-generic #11-Ubuntu SMP Tue Feb 13 18:23:35 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
sudo dmidecode -t 1
# dmidecode 3.1
Getting SMBIOS data from sysfs.
SMBIOS 2.7 present.
Handle 0x0001, DMI type 1, 27 bytes
System Information
Product Name: LIFEBOOK A555
Version:
Serial Number: YM3M035369
UUID: CF0F380B-
Wake-up Type: Power Switch
SKU Number:
Family: LIFEBOOK-FTS
Best Regards,
Marek
affects: | ubuntu → mesa (Ubuntu) |
Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https:/ /wiki.ubuntu. com/Bugs/ FindRightPackag e. You might also ask for help in the #ubuntu-bugs irc channel on Freenode.
To change the source package that this bug is filed about visit https:/ /bugs.launchpad .net/ubuntu/ +bug/1752343/ +editstatus and add the package name in the text box next to the word Package.
[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]