Description of problem: LXDE plays sound fine for about a day or so, then loses sound completely. Version-Release number of selected component (if applicable): M3 LXDE 3.5 Virtualbox 4.2.12 OSE guest How reproducible: Very, though difficult to determine how long it takes to lose sound Steps to Reproduce: 1. Run LXDE desktop 2. Play music, etc -- maybe leave Pandora running for long periods of time. 3. (at some point, sound quits) Here is some additional info. At first, I thought this was a sound driver issue, but apparently it is not. It does not appear to be virtualbox or pulseaudio-related, involving neither the host or guest environments generally. After much investigation, I have determined this to be related to the login session. I tried killing off the guest pulseaudio, but that just starts a new pulseaudio session, and still no sound. However, if I log in to a new LXDE session, it seems to reset the sound somehow and I have sound in that session! If I return to the original login session, there is still no sound. I do not know yet if this is LXDE-specific only, or if this may be true of other DE's as well. I also don't know if this is userID-specific or not, because I have not tried logging out and back in on the same user id. And I don't know how long it takes or what set of conditions will bring about the loss of sound. If there are LXDE sound controls (meaning beyond Mageia OS's sound controls), let me know and I will try them. Reproducible: Steps to Reproduce:
I tried logging out of my 1st session/1st user to see if the same thing happens for my 1st user. But upon logout, the whole system hung up! I could not access the other virtual terminal where the 2nd user was still logged in. I could see some disk and network i/o periodically, but it wasn't until I had VBox send a shutdown signal that the VM finally shut down. I did take a VBox snapshot beforehand so I can revisit this later if needed. The next time my first userID loses sound in its LXDE session, I will try to log out and log back in -- this will be a slightly different scenario because I will not try to use a second user.
I switched from lightdm to lxdm this seems to correct the sound problem because I have now had the system running for 3 days without sound problems (other than some playback choppiness from time to time, but that could be other issues, and most of the time I get excellent sound). It also seems to correct the problem with the login screen #10358. I will leave M3 running for a few more days before avering that this is really solved.
My conclusions in #10356 comment 2 are not correct. I was not assessing this problem thoroughly enough, basing my conclusions on only a few variations and little repetition (mostly due to my own schedule). I set up a VM for testing M3 separately from the VM I use for my actual work on projects, etc. This test VM is a virgin install with LXDE only (from Mageia-3-i586-DVD.iso). I did not install any other desktops. Using this VM instead of my working VM, I was able to ascertain behavior patterns. What I am noticing -- and this seems to be consistent -- is that cold booting in full screen mode to the lxdm/lxde greeter corrupts the screen display. Note that I do not log in or modify anything in the system. Warm booting does not do this; the screen will display correctly. Also, warm or cold booting the VM in Window mode to the lxdm/lxde greeter does not corrupt the screen. I performed this test just now about 10 times for each configuration (thankfully, my hardware is fast). I would say I have performed these tests adequately to make this conclusion so far. PCLinuxOS LXDE spin uses gdm, and that distro has never given me problems like this. Since both PCL and Mga are kind of "sister" distros in a sense, I may try gdm as a test, as well as lightdm. I am not sure if/how sounds is or is not affected by the chosen login or display manager. One problem is that it seems to take a day or more for audio loss to occur, so testing various combinations may take some time. I am posting this remark in both bugs.
CC: (none) => bozonius
Hi, maybe related to #11071 ? I've got the same bug with lightdm and lxdm.
CC: (none) => julien.moragny
I would not know; command line was not part of my own attempts to recreate the bug. It does not really sound related, though. Note that the scenario I reported was happening in a VirtualBox VM, and I noted that it looked like the host sound daemon was experiencing some kind of a problem. I have not experienced this bug for a long time now. AFAIC, you may close this bug. I can re-open or re-file it if it happens again.
in what dm what this happening ?
See comment 3 above. It looks like I was using lxde/lxgreeter, per notes.
Mageia 3 changed to end-of-life (EOL) status 4 months ago. http://blog.mageia.org/en/2014/11/26/lets-say-goodbye-to-mageia-3/ Mageia 3 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