[upstream] OpenOffice can't handle burn:// URLs - gvfs doesn't export it normally
Bug #120069 reported by
Colin Fletcher
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
gvfs |
Expired
|
Medium
|
|||
gvfs (Ubuntu) |
Invalid
|
Low
|
Unassigned | ||
openoffice.org (Ubuntu) |
Won't Fix
|
Wishlist
|
Unassigned |
Bug Description
Drag an OpenOffice file (I've tried it with an .odt file) into the CD/DVD Creator. Then double-click it there.
OpenOffice starts up, but then shows a message "General Internet error has occurred" and doesn't open the file.
I believe that this used to work in Edgy, though I can't try it any more. It seems similar to Bug #47461, though.
Changed in openoffice.org: | |
importance: | Medium → Low |
Changed in openoffice.org: | |
status: | Confirmed → In Progress |
Changed in openoffice.org: | |
importance: | Low → Wishlist |
Changed in openoffice.org: | |
status: | In Progress → Triaged |
Changed in openoffice.org: | |
milestone: | jaunty-alpha-1 → ubuntu-9.04-beta |
Changed in gvfs: | |
status: | Unknown → Invalid |
Changed in gvfs: | |
status: | Invalid → Unknown |
Changed in gvfs: | |
status: | Unknown → Confirmed |
Changed in openoffice.org: | |
assignee: | ccheney → nobody |
milestone: | ubuntu-9.04-beta → none |
Changed in gvfs: | |
importance: | Unknown → Medium |
Changed in openoffice.org (Ubuntu): | |
status: | Triaged → Won't Fix |
Changed in gvfs: | |
status: | Confirmed → Expired |
Changed in gvfs (Ubuntu): | |
importance: | Undecided → Low |
status: | Confirmed → Invalid |
To post a comment you must log in.
I don't get "General Internet error has occurred" here (Hardy, 1:2.4.0~ rc2-1ubuntu3) , but OOo still silently fails to open the burn:/// URL. Perhaps converting OOo over from gnome-vfs to gvfs would help matters? I note that the gvfs-* command-line tools seem to be able to cope with burn:/// while gnomevfs-* can't.
The gstreamer fix in the other bug you mention doesn't seem to be applicable; it registers its own gnome-vfs handlers rather than just being a client of gnome-vfs, so it's in a different situation.