<div dir="ltr">Here are a few miscellaneous problem I noticed with f10beta live USB. I tried to have a persistent overlay, but while booting, I noticed a message "Unable to find persistent overlay". After booting, alsamixer doesn't work for me: [fedora@localhost ~]$ alsamixer I: caps.c: Limited capabilities successfully to CAP_SYS_NICE. I: caps.c: Dropping root priviliges. I: caps.c: Limited capabilities successfully to CAP_SYS_NICE. ALSA lib pulse.c:266:(pulse_connect) PulseAudio: Unable to connect: Connection refused alsamixer: function snd_ctl_open failed for default: Connection refused I've always had problems with PulseAudio, so I tried to remove it: yum remove pulseaudio Loaded plugins: refresh-packagekit Setting up Remove Process Could not retrieve mirrorlist <a href="http://mirrors.fedoraproject.org/mirrorlist?repo=rawhide&arch=i386">http://mirrors.fedoraproject.org/mirrorlist?repo=rawhide&arch=i386</a> error was [Errno 4] IOError: <urlopen error (-2, 'Name or service not known')> Error: Cannot retrieve repository metadata (repomd.xml) for repository: rawhide. Please verify its path and try again ______ System->Preferences->Hardware->Sound ->Test Sound Capture: gconfaudiosrc ! audioconvert ! audioresample ! gconfaudiosink profile=chat: Could not open audio device for recording. _______ [fedora@localhost ~]$ totem Segmentation fault [fedora@localhost ~]$ totem I: caps.c: Limited capabilities successfully to CAP_SYS_NICE. I: caps.c: Dropping root priviliges. I: caps.c: Limited capabilities successfully to CAP_SYS_NICE. I: caps.c: Limited capabilities successfully to CAP_SYS_NICE. I: caps.c: Dropping root priviliges. I: caps.c: Limited capabilities successfully to CAP_SYS_NICE. I: caps.c: Limited capabilities successfully to CAP_SYS_NICE. I: caps.c: Dropping root priviliges. I: caps.c: Limited capabilities successfully to CAP_SYS_NICE. I: caps.c: Limited capabilities successfully to CAP_SYS_NICE. I: caps.c: Dropping root priviliges. I: caps.c: Limited capabilities successfully to CAP_SYS_NICE. The program 'totem' received an X Window System error. This probably reflects a bug in the program. The error was 'BadAlloc (insufficient resources for operation)'. (Details: serial 46 error_code 11 request_code 140 minor_code 19) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the --sync command line option to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.) </div>