Samsung ARM Chromebook reboots upon starting Audacity

[shaunhey]

Thanks for all of your hard work on Crouton! I still can't believe how well this all works together, giving me a lighweight and inexpensive, yet fully functional laptop with fantastic battery life!

I decided I wanted to do something with Audacity this morning, so I went through the typical "apt-get install audacity". But when I tried to start audacity, my Chromebook rebooted. When I try to launch it from a terminal window, I can see something about a jack server just before the reboot. I'm not terribly familiar with the state of audio on Linux, but I have a feeling the chroot and Chrome OS are probably fighting over the sound device. Issue #111 sounded similar.

Any ideas what could be going on? My crouton chroot is raring running xfce4.

Thanks!

[dnschneid]

Hey, that's a pretty cool Chromium OS bug! Meanwhile, Audacity in quantal works fine.

[dnschneid]

Cool. I can launch it once upon reboot, and then the second time crashes the system...

[shaunhey]

Thanks for checking! Note: I tried installing the xfce target for quantal but it fails on xserver-xephyr.

[dnschneid]

Oh, right. Raring expects kernel 3.8, while Chromium OS is still on 3.4 (it's in the progress of migrating to 3.8, but not quite there yet). I'd bet Audacity is trying to use some >3.4 feature of ALSA that isn't available on 3.4, although that really shouldn't cause a reboot.

Anyway, the Xephyr install on Quantal works for me; try it again and post any errors that get spit out.

[Mouse75]

I had similar matter but without any reboot, audacity crash immediatly just open, and also audacios
or xine when i tryed to play mp3 files.
I have fixed installing the package
libmad0 0.15.1b7 for arm Wheezy from Debian repository
instead of libmad0 0.15.1b-7ubuntu2 it's seems bugged.
Now i have forced this version and all work great
audacity, gnome mplayer and XIne
Thanks a lot for crouton and Your work and to david for the suggestion about libmad0 i have found in another post.

[abudda]

I have also been having my Chromebook reboot when I start Audacity.

I'm running on a Samsung ARM Chromebook (Model XE303C12-A01US, brand new as of two weeks ago).

Using crouton to run Ubuntu, I have installed the xfce target for quantal (I tried a number of other targets and releases, but am using this one on the advice in this thread)

I get the following error appear on the terminal screen for several seconds before it reboots:

---

ALSA lib pcm.c:2217:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.front
ALSA lib pcm.c:2217:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.rear
ALSA lib pcm.c:2217:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.side
(a whole lot more similar messages)
ALSA lib pcm_dmix.c:957: (snd_pcm_dmix_open) The dmix plugin supports only playback stream
ALSA lib pcm_dmix.c:1018:(snd_pcm_dmix_open) unable to open slave
Cannot connect to server socket err = No such file or directory
Cannot connect to server request channel
jack server is not running or cannot be started

---

I've tried a number of ideas without success, tried compiling audacity from source, tried installing an older version (2.0.0-1), tried manually installing the libmad0 package suggested in the comment above, and I still get the same behaviour.

Any ideas/suggestions would be greatly appreciated, thanks!

[dnschneid]

If it's happening on Quantal, then it's definitely an issue with Chromium OS. I'll update with a bug number once I've filed one.

[abudda]

Thanks David. Yes, it's definitely happening on Quantal, I set it up via:

sudo sh -e ~/Downloads/crouton -t xfce -r quantal

[drinkcat]

FYI, I may have bumped into a similar bug with the latest Chrome OS Stable release (4100.89.0). I believe it's a kernel driver bug, likely only affecting the Samsung ARM Chromebook.

I reported the bug to Chromium bug tracker: https://code.google.com/p/chromium/issues/detail?id=275073 (star the issue if you want to receive updates, but do not comment unless you have something to add).

[dnschneid]

Oh, that's definitely it. Audacity has the poor behavior of opening and closing pretty much every ALSA device when it launches.

[dnschneid]

This is actually one of the few audio issues that won't be fixed by #343, because Audacity will poll the other ALSA devices anyway (unless we remove the user from the audio group, which is an option).

[dnschneid]

Closing; discussion can continue in #343.

[joro10]

hello guy i download crouton for the wed side but then im trying to run it says it cant open can u guys help me out thanks a lot