Description of problem: pam_console seems to be missing the files needed to cause /dev/dri/cards* to be read/writable via the user. This causes hardware acceleration of DRI to fail. Version-Release number of selected component (if applicable): boot up mageia /dev/dri/cards* not read/writeable use glxinfo and see that mesa is using software raster set /dev/dri/cards* to read/writable X now has hardware acceleration How reproducible: Steps to Reproduce: 1. 2. 3.
Sorry for responding to your report so late, we are very short on triagers. Is the problem still there with current version pam-1.1.3-5.mga2 ? cc'ing submitter of pam
Keywords: (none) => NEEDINFOCC: (none) => mageia, marja11
Joseph, are you using systemd? If so, make sure you do not have rpmnew files in /etc/pam.d/ specifically a system-auth.rpmnew I strongly suspect that you are missing the line: -session optional pam_systemd.so This in turn means that logins are not tracked properly and ACLs are not written on /dev/dri/* /dev/snd/* etc. If this is the case, it's essentially the same problem as here: https://bugs.mageia.org/show_bug.cgi?id=2982
@ Joseph Please reply to comment 1 and comment 2 within two weeks from now, to avoid this bug being closed as OLD.
OK, this is a pretty strange one. There appear to be three "Master" controls, and no specific separate ones for Headphones etc. I suspect something is messing up with the model of this driver but will consult with some colleagues on it.
Status: NEW => ASSIGNED
Please ignore the above comment, it was meant for #212
Reset to New after my own silliness :)
Status: ASSIGNED => NEW
(In reply to comment #3) > @ Joseph > > Please reply to comment 1 and comment 2 within two weeks from now, to avoid > this bug being closed as OLD. giving you 2 weeks extra time, please ignore comment 4, 5 and 6
Since there are insufficient details provided in this report for us to investigate the issue further, and we have not received feedback to the information we have requested above, we will assume the problem was not reproducible, or has been fixed in one of the updates we have released for the reporter's distribution. Users who have experienced this problem are encouraged to upgrade to the latest update of their distribution, and if this issue turns out to still be reproducible in the latest update, please reopen this bug with additional information. Closing as OLD.
Status: NEW => RESOLVEDResolution: (none) => OLD