Rene, Thanks for the response. Sorry this came through twice. The first report had some typos in it. I'm glad you merged them. Apologies also if I didn't understand the severity rating system properly. It seemed to me this bug did render the openoffice.org-gnome vfs interface unusable - although I accept smb isn't the only protocol gnome vfs provides - however as I thought it was the function of this package to provide the gnome-vfs interface, this was why I rated it as grave. Sorry again, I don't have sid available for testing. I wasn't aware there were OO builds on backports.org, but I will try these. Struan on 18/06/07 13:05 Rene Engelhard wrote : severity 429475 important severity 429473 important merge 429473 429475 tag 429473 + moreinfo thanks Struan Bartlett wrote:Version: 2.0.4.dfsg.2-7etch1 Justification: renders package unusableNonsense. It does not render the full office suite unusable that you can't write to some particular place.To reproduce this bug, I load oowriter, create a new empty document, go to File->Save As and type in a samba share e.g. 'smb://machine/myshare' and hit enter. When the samba share loads up in the dialog, I then double-click on any subdirectory. At this point openoffice crashes with error. Sometimes it crashes on first calling up of 'smb://machine/myshare'. The error message is always like e.g.: *** glibc detected *** free(): invalid pointer: 0xb74f76e0 *** N.B. I can reproduce this bug identically on two etch machines (and haveAnd on sid? And with the OOo from www.backports.org on etch?Instead my guess is that we have a bug in the structures created by /usr/lib/openoffice/program/ucpgvfs1.uno.so - which would make this an openoffice.org-gnome bug.Maybe, there at least were fixes there in the development after 2.0.4 iirc. [ And why are you filing this two times? ] Grüße/Regards, René |