Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 237322 - Totem spews error upon startup on livecd
Totem spews error upon startup on livecd
Product: Fedora
Classification: Fedora
Component: totem (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Bastien Nocera
: Reopened
Depends On:
Blocks: Fedora7LiveCD
  Show dependency treegraph
Reported: 2007-04-20 15:42 EDT by Jarod Wilson
Modified: 2007-11-30 17:12 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2007-04-24 09:03:29 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Jarod Wilson 2007-04-20 15:42:41 EDT
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 15:55:28 EDT
This doesn't happen to be a box without a sound card does it?
Comment 2 Jarod Wilson 2007-04-20 16:45:02 EDT
D'oh. Yeah.
Comment 3 Bastien Nocera 2007-04-20 18:48:29 EDT
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-20 23:35:44 EDT
Graphical dialog, after launching totem from the gnome applications menu.
Comment 5 Bastien Nocera 2007-04-23 10:38:36 EDT
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 13:26:27 EDT
Upstream at:
Comment 7 Bastien Nocera 2007-04-24 09:03:29 EDT
Fixed upstream. I'll push it in the next 2.18 update.
Comment 8 David Timms 2007-05-02 06:59:33 EDT
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.