Whenever I cut and paste page into oowriter images are not shown. Just rectangles with some text inside. No networking configuration options affects this. As this problem happens only with openoffice and doesn't happen with openoffice-bin this is Gentoo build problem and upstream closed similar bug as invalid: http://www.openoffice.org/issues/show_bug.cgi?id=67048 This problem is reproducible on all 2.X versions of openoffice and is regression from 1.x branch. For further details take a look at bug mentioned above. Thank you for your time.
The attached test document in upstream bugreport works just fine here, ~amd64. [ebuild R ] app-office/openoffice-2.4.0.9999_pre14 USE="branding cups dbus gnome gstreamer gtk java jemalloc opengl openxml pam webdav xulrunner -access -binfilter -debug -eds -firefox -helpless -kde -ldap -mono -odbc -odk -seamonkey"
Hi Peter, Still can reproduce the problem here. If it doesn't show in openoffice-bin it is an ooo-build-problem, so in this case we have another upstream. Could you please file this at: https://bugzilla.novell.com/index.cgi (in the future there should be a proper go-oo / ooo-build bugzilla, until then we should use the novell one...) Sorry about all this being such a tedious task... Still interesting that Hanno can't reproduce it...
I've built OO with Hanno's USE flags and OO shows images. Andreas, I'm going to localize the problem to a single USE flag (if posible) before I report this bug at novel bugzilla but taking into account the time OO build takes this will not happen in nearest two-tree days. :)
(In reply to comment #3) > I've built OO with Hanno's USE flags and OO shows images. Andreas, I'm going to > localize the problem to a single USE flag (if posible) before I report this bug > at novel bugzilla but taking into account the time OO build takes this will not > happen in nearest two-tree days. :) > I'd bet on the webdav-flag (which enables neon) in this case.
(In reply to comment #4) > I'd bet on the webdav-flag (which enables neon) in this case. Yep, that's it. Just rebuilt with webdav use-flag enabled and the document works fine now. As this is a feature regression, I guess the best solution would be to just drop the webdav use-flag and add a fixed dependency on neon, any comments, objections on this?
Still strange that some urls work and some not...
Hanno, what do you mean? Give us examples. The attached document to that bug is way too old so it could contain links to nonexistent images... I've reopened upstream bug report. Until this bug is fixed I thinkg it's good idea to drop webdav USE flag with some comments in ebuild...
(In reply to comment #7) > Hanno, what do you mean? Give us examples. Your report in OOo IZ states: "... may be problem is because image url starts not with http://www. but http://img. in my case. And I tried another pages and thew worked, and images there started with http://www . ..." So, ..., as far as I see they should fix their engine to load images from any site without the need of webdav. Sounds just broken to me to use webdav there. Instead it should just use curl. Which it does for URLs starting with "http://www". Not? :) > The attached document to that bug is > way too old so it could contain links to nonexistent images... That odt shows the images just fine.
(In reply to comment #8) > (In reply to comment #7) > > Hanno, what do you mean? Give us examples. > > Your report in OOo IZ states: You should read the whole bug report next time. Take a look at my update there on (Sat Feb 16): in the last versions of openoffice it's impossible to load ANY pictures at all. There is no possibility to update bugzilla entries that's why initial information is still there but OUTDATED and that's why developers have to read all entries in bugzilla and that's why all developers hate any noise in bugzilla. Thus if you unable to reproduce some new problem with openoffice built with or without wedav USE flag then it's better to keep silence. Thank you.
Well, it is still stupid to use webdav for loading data from internet. OOo has curl already. Or what is curl for? So, their engine should still be rewritten/corrected/whatever to use curl. ;) Or they should drop curl depend.
Ok, this is fun. My resumee: Neon has other features for webdav than libcurl. So I guess OOo devs want to stay with it. Neon has no feature for ftp protocol. So no option to drop libcurl. Until neon supports ftp protocol, if ever. So I will do a sub-module to support http/https with libcurl if neon is disabled. Though, I am busy and do not know when I find the time. Until then the USE flag 'webdav' must go. Have fun! :)
(In reply to comment #11) > > Until then the USE flag 'webdav' must go. Which is actually what I did for OOo 2.4.1_rc2, so I guess we can close this bug, as the rest is more of an enhancement for the future...
