[gstreamer-bugs] [Bug 328423] New: [gnomevfs] doesn't handle case when gnomevfs can't init
GStreamer (bugzilla.gnome.org)
bugzilla-daemon at bugzilla.gnome.org
Tue Jan 24 05:03:24 PST 2006
Do not reply to this via email (we are currently unable to handle email
responses and they get discarded). You can add comments to this bug at
http://bugzilla.gnome.org/show_bug.cgi?id=328423
GStreamer | gst-plugins-base | Ver: HEAD CVS
Summary: [gnomevfs] doesn't handle case when gnomevfs can't init
Product: GStreamer
Version: HEAD CVS
Platform: Other
OS/Version: Linux
Status: NEW
Severity: normal
Priority: Normal
Component: gst-plugins-base
AssignedTo: gstreamer-bugs at lists.sourceforge.net
ReportedBy: wingo at pobox.com
QAContact: gstreamer-bugs at lists.sourceforge.net
GNOME version: Unspecified
GNOME milestone: Unspecified
There are cases when gnomevfs can't init. Mostly this is if there is no
~/.gnome2 directory, and that directory can't be made. However our plugin
doesn't check the return value of gnome_vfs_init(), just assuming that it
succeeds.
Either we:
- call _init in the instance init, as we do now, and store the result in a
variable that makes the plugin refuse to go to READY
- call _init() in NULL->READY
- call _init() in the plugin init
- somehow make upstream not check for .gnome2 (why does it need it?) -- but
it's possible there are other ways it can fail (e.g. bonobo)
c.f. https://core.fluendo.com/flumotion/trac/ticket/278
--
Configure bugmail: http://bugzilla.gnome.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
You are the assignee for the bug.
More information about the Gstreamer-bugs
mailing list