Bug 237322 - Totem spews error upon startup on livecd
Summary: Totem spews error upon startup on livecd
Alias: None
Product: Fedora
Classification: Fedora
Component: totem
Version: rawhide
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Bastien Nocera
QA Contact:
Depends On:
Blocks: Fedora7LiveCD
TreeView+ depends on / blocked
Reported: 2007-04-20 19:42 UTC by Jarod Wilson
Modified: 2007-11-30 22:12 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2007-04-24 13:03:29 UTC
Type: ---

Attachments (Terms of Use)

Description Jarod Wilson 2007-04-20 19:42:41 UTC
Description of problem:
Totem on the F7 livecd (actually, running it off a usb key) spits out an error
on startup:

An error occurred
Could not open resource for writing.

Version-Release number of selected component (if applicable):
totem 2.18.1-1.fc7.i386
f7 livecd image from 2007-04-11

How reproducible:
Boot off live media, launch Movie Player from Applications menu.

Comment 1 Jeremy Katz 2007-04-20 19:55:28 UTC
This doesn't happen to be a box without a sound card does it?

Comment 2 Jarod Wilson 2007-04-20 20:45:02 UTC
D'oh. Yeah.

Comment 3 Bastien Nocera 2007-04-20 22:48:29 UTC
Is this an error on the command-line, or a dialogue? If the latter, then it's
not normal, and should have been fixed before totem 2.18.0.

Comment 4 Jarod Wilson 2007-04-21 03:35:44 UTC
Graphical dialog, after launching totem from the gnome applications menu.

Comment 5 Bastien Nocera 2007-04-23 14:38:36 UTC
Actually, it's the autoaudiosink that throws up an error, and Totem is usable
after dismissing the dialogue. Still, it shouldn't even complain...

Comment 6 Bastien Nocera 2007-04-23 17:26:27 UTC
Upstream at:

Comment 7 Bastien Nocera 2007-04-24 13:03:29 UTC
Fixed upstream. I'll push it in the next 2.18 update.

Comment 8 David Timms 2007-05-02 10:59:33 UTC
Oops, missed this bug when me tooing another bug. For a screenshot of probably
the same unfriendly error on f7t4 upgraded from fc6, see:

Note You need to log in before you can comment on or make changes to this bug.