Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#42719 - [chromium] can't use hardware acceleration with Intel G43/45 graphic card
Attached to Project:
Arch Linux
Opened by guoqiyi (guoqiyi) - Sunday, 09 November 2014, 03:15 GMT
Last edited by Evangelos Foutras (foutrelis) - Tuesday, 31 March 2015, 17:35 GMT
Opened by guoqiyi (guoqiyi) - Sunday, 09 November 2014, 03:15 GMT
Last edited by Evangelos Foutras (foutrelis) - Tuesday, 31 March 2015, 17:35 GMT
|
DetailsDescription:
As the summary said,when I choose to use "hardware acceleration" option,Chromium will always make the whole screen freeze occasionally,and error messages will fill the /var/lib/systemd/coredump directory.It exists for a long time until I find it's caused by the conflict between Chromium and mesa driver.Hope to fix it. Additional info: * package version(s) * config and/or log files etc. Steps to reproduce: |
This task depends upon
Closed by Evangelos Foutras (foutrelis)
Tuesday, 31 March 2015, 17:35 GMT
Reason for closing: No response
Additional comments about closing: No response regarding whether or not the ignore-gpu-blacklist flag was enabled.
Tuesday, 31 March 2015, 17:35 GMT
Reason for closing: No response
Additional comments about closing: No response regarding whether or not the ignore-gpu-blacklist flag was enabled.
2014-11-09 10:45:04 的屏幕截图.png
FS#42110?At any rate, this isn't something I can investigate myself as I don't use Intel graphics or GNOME (which could be related). You might have better luck checking if Chrome has the same issue and then reporting it upstream.
@Javier: Is this still an issue for you?