I'm using XUbuntu on an HP OmniBook 2100, with 288 MB SDRAM and plenty of room in HDD. Whenever I try to play a sound file, no matter if its format is wma, mp3 or whatever, Parole shuts itself down as soon as the file is open and tries to play it. Just for you to know: Exaile has the same behavior, shutting itself down as soon as it is ready to play the file. Nautilus is pretty capable of playing the files, even if limited to its auto-play time span. Totem has no problem to play any audio file. You see this computer has no resources to waste, so I'd rather use Parole instead of Totem, as soon as it works. In case I can be of any help, please give me your instructions. Kind regards. Antonio Rodulfo
I'm sorry for the late reply, the thing is that i don't know from where to start, it is weired. Is the player is shutting down normally, or it is getting killed by the kernel, you can check after with "dmesg" in the terminal to see if you ran out of memory...
(In reply to comment #1) > I'm sorry for the late reply, the thing is that i don't know from where to > start, it is weired. > > Is the player is shutting down normally, or it is getting killed by the kernel, > you can check after with "dmesg" in the terminal to see if you ran out of > memory... I am sorry as well. I've had to focus on other things. I upgraded my XUbuntu 10.10 to 11.04, with everything it needed, and tried again. Parole keeps disappearing as soon as it tries to open and reproduce the first song. I run dmesg before and after trying Parole, so I could easily detect any change: no way. There's nothing to comment about, no clue for you. I can use Totem, as before, and I can now use Exaile as well, but only if I don't ever try to change playing volume from included control. Otherwise, if I try to change volume from Exaile's control, it shuts down immediately. Any clue? Any hint as to what I can do to help solving this issue? Kind regards, Antonio Rodulfo
Can you please test current git master and see whether you can reproduce the problem?
I haven't found any way to reproduce your problems. Please try with the new version (0.3.0) and if the bugs re-appears please re-report and we'll try to get to the bottom of it.