Glamor is broken in mageia 4 when i try to set it on it will show error,it's fixed in upstream version. Reproducible: Steps to Reproduce:
Created attachment 5116 [details] Error log Error log of glamor.
Attachment 5116 mime type: application/octet-stream => text/plain
Keywords: (none) => TriagedAssignee: bugsquad => thierry.vignaudSource RPM: (none) => glamorSummary: Glamor is broken in mageia 4 => Glamor is broken in mageia 4 - Failed to load module "glamoregl"
It seems opensuse did have same bug but they only fixed it in opensuse. https://bugzilla.novell.com/show_bug.cgi?id=766513#c19
Not sure it is the same issue, but glamor still seems to be broken on mageia 4.1 [ 713.427] (EE) Failed to load /usr/lib64/xorg/modules/libglamoregl.so: /usr/lib64/xorg/modules/libglamoregl.so: undefined symbol: _glapi_tls_Context which means no XV on many newer radeon cards with the open source driver.
CC: (none) => herbert
two problems with glamor support in Mageia4 (apart that you need to manually configure & install stuff): * undefined symbol: _glapi_tls_Context â mesa needs to be compiled with --enable-glx-tls If you fix that, you might run into the next problem (symptoms: boots up OK, with kernel messages/graphical boot-progress, but when X is started, monitors turns off/doesn't receive signal anymore) * /usr/lib64/xorg/modules/drivers/radeon_drv.so: undefined symbol: glamor_xv_init â glamor nees update to 0.6.0 / version that has that funtionality (and corresponding --enable-xv switch, that is default in 0.6.0) ##### In other words to fix for Mageia 4, it needs 1) fix to mesa-package and 2) backport of glamor package
CC: (none) => lohmaier+mageia
Thx christian for your explain that problem,i can confirm that it works with sandy bridge intel hd 3000 out of box in beta 3.
I will close this bug because i already get glamor working in mageia 5 so there is no any need to get it working in mageia 4.
Status: NEW => RESOLVEDResolution: (none) => WORKSFORME
reopen - while it is nice that the problem is solved in an upcoming version, Mageia 4 still suffers from the problem. So package maintainers can close this wontfix if they don't think it is worth fixing (although fixing is simple, see comment#4) but at least accorting to mageia's support page: "Mageia 4 will be supported until August 1st, 2015."
Status: RESOLVED => REOPENEDResolution: WORKSFORME => (none)
CC: (none) => tmb
No not anymore fixed intel have removed glamor from their driver. https://wiki.archlinux.org/index.php?title=Intel_graphics&diff=365331&oldid=361474
While this might fix it for intel, it is still broken for radeon cards. Best, Herbert
It was only fixed in Mageia 5 not in Mageia 4.
(In reply to Christian Lohmaier from comment #7) > reopen - while it is nice that the problem is solved in an upcoming version, > Mageia 4 still suffers from the problem. > > So package maintainers can close this wontfix if they don't think it is > worth fixing (although fixing is simple, see comment#4) but at least > accorting to mageia's support page: "Mageia 4 will be supported until August > 1st, 2015." Fix is simple but we have no backports open so to fix need to break version policy as plan is to open backports only to Mageia 5. Second thing is nvidia and ati have it but it's very unstable cause lot of crashes,fglrx are not supported so it's only usable with free drivers so this fix going to break our stability ??? yes. I really suggest therry will close this as resolved wont fix.
(In reply to Otto Leipälä from comment #11) > > Fix is simple but we have no backports open so to fix need to break version > policy as plan is to open backports only to Mageia 5. That's a shame, but is a plausible reason to close this bug. > Second thing is nvidia and ati have it but it's very unstable cause lot of > crashes, Not from my experience. But I use my machine only with gnome3 to browse the web, do work and watch videos, so apart from what gnome does with 3d, I don't use 3d otherwise... > fglrx are not supported so it's only usable with free drivers "only" is not the right word here. the open source driver works much better for video playback for me. (AMD A4-5000 APU) With fglrx watching videos was painful, as despite configuring the avoid tearing setting in the settings, there still was lots of tearing/artifacts (using 2560x1440 resolution). The free driver works much better. > so > this fix going to break our stability ??? yes. I don't see why it would break stability, as the fix won't switch your x-settings to use glamor, this would still require manual configuration (in fact when you configure opensource driver with control center, you get ~unusable system, as glamor is not switched on, and thus you get the software-rendering only). You can continue to use fglrx just as before, if that is what you define with stability. Right now, you can only use fglrx on Mageia4 (unless you compile/replace the packages yourself), since otherwise gnome would render with software/CPU and that not only wastes computing resources, but of course is noticeably slower. > I really suggest therry will close this as resolved wont fix. Fine if he doesn't want to touch it because of the no-backports policy (or if he as maintainer thinks it is not worth it/he won't do it for whatever reason), but not just because "fixed in Mageia 5".
"only" is not the right word here. the open source driver works much better for video playback for me. (AMD A4-5000 APU) With fglrx watching videos was painful, as despite configuring the avoid tearing setting in the settings, there still was lots of tearing/artifacts (using 2560x1440 resolution). The free driver works much better. Yes you are right main problem is in gnome-shell you can't use nonfree drivers as they are know not to work with gnome very well.
Mageia 4 changed to end-of-life (EOL) status on 2015-09-19. It is is no longer maintained, which means that it will not receive any further security or bug fix updates. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Mageia version. Bug Reporter: Thank you for reporting this issue and we are sorry that we weren't able to fix it before Mageia 4's end of life. If you are able to reproduce it against a later version of Mageia, you are encouraged to click on "Version" and change it against that version of Mageia. If it's valid in several versions, select the highest and add MGAxTOO in whiteboard for each other valid release. Example: it's valid in cauldron and Mageia 5, set to cauldron and add MGA5TOO. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Mageia release includes newer upstream software that fixes bugs or makes them obsolete. If you would like to help fixing bugs in the future, don't hesitate to join the packager team via our mentoring program [1] or join the teams that fit you most [2]. [1] https://wiki.mageia.org/en/Becoming_a_Mageia_Packager [2] http://www.mageia.org/contribute/
As announced over a month ago, Mageia 4 changed to end-of-life (EOL) status on 2015-09-19. It is is no longer maintained, which means that it will not receive any further security or bug fix updates. This issue may have been fixed in a later Mageia release, so, if you still see it and didn't already do so: please upgrade to Mageia 5 (or, if you read this much later than this is written: make sure you run a currently maintained Mageia version) If you are able to reproduce it against a maintained version of Mageia, you are encouraged to 1. reopen this bug report, by changing the "Status" from "RESOLVED - OLD" to "REOPENED" 2. click on "Version" and change it against that version of Mageia. If you know it's valid in several versions, select the highest and add MGAxTOO in whiteboard for each other valid release. Example: it's valid in cauldron and Mageia 5, set to cauldron and add MGA5TOO. 3. give as much relevant information as possible. If you're not an experienced bug reporter and have some time: please read this page: https://wiki.mageia.org/en/How_to_report_a_bug_properly If you see a similar issue, but are _not_sure_ it is the same, with the same cause, then please file a new bug report and mention this one in it (please include the bug number, too). If you would like to help fixing bugs in the future, don't hesitate to join the packager team via our mentoring program [1] or join the teams that fit you most [2]. [1] https://wiki.mageia.org/en/Becoming_a_Mageia_Packager [2] http://www.mageia.org/contribute/
Status: REOPENED => RESOLVEDResolution: (none) => OLD