Under udev 181, it is not possible for userland users to have sound when sysvinit is used instead of systemd. The old udev 173, which deprecates the alsa acl rules to set permissions for system users. That function was taken over by systemd. So as a result, the Alsa sound card spawns with default permissions of 660 which means that normal users can't get sound. Please advise.
What's wrong with systemd? Why can't you use it? In Mageia 3 there will be no SysVinit.
Keywords: (none) => NEEDINFOCC: (none) => sander.lepik
Thats not the point. in Mga2 we officially support sysvinit setups... Colin, thoughts on the issue ?
CC: (none) => mageia, tmb
This shouldn't matter. The udev shipped with mga2 should have udev-acl support. I'm not aware of any specific ACL problems on mga2 regarding this, so will have to test in a VM at some point. IIRC I saw Zombie asking on #systemd today about broken raid setups (but disappeared before I could ask if he was using Mageia on that setup. If this is your reason for using sysvinit over systemd we can look at that too (depending on your exact raid setup it may be done partially by dracut but also by the fedora-* services which we support under mageia to start raid setups). I suspect however you're getting bitten by the dmraid->mdraid shakeup - but anyway it is a separate issue. Please feel free to add me on any bug you open about that.
As far as sound goes, I did a work around by editing the alsa udev rules to create ALSA block devices with permissions of 666 rather than 660, this isn't a proper solution, I know, but it works. Under Systemd, you wind up with permissions of cr-rw----+ but under sysvinit, it's just cr-rw----. my change to udev makes the default permissions cr-rw-rw- instead. The RAID issue is separate. Under systemd, RAID volumes block don't appear. So the system boots in emergency mode.
(In reply to comment #4) > The RAID issue is separate. Under systemd, RAID volumes block don't appear. So > the system boots in emergency mode. Is there separate bug about it? If not, are you willing to create one?
Yes.
This message is a reminder that Mageia 2 is nearing its end of life. Approximately one month from now Mageia will stop maintaining and issuing updates for Mageia 2. At that time this bug will be closed as WONTFIX (EOL) if it remains open with a Mageia 'version' of '2'. 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 prior to Mageia 2's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Mageia 2 is end of life. If you would still like to see this bug fixed and 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. 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. -- The Mageia Bugsquad
Mageia 2 changed to end-of-life (EOL) status on ''22 November''. Mageia 2 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Mageia please feel free to click on "Version" change it against that version of Mageia and reopen this bug. Thank you for reporting this bug and we are sorry it could not be fixed. -- The Mageia Bugsquad
Status: NEW => RESOLVEDResolution: (none) => OLD