Hi--

Just upgraded from Ubuntu 8.04 lts to 10.04 lts. Now OOo crashes about half the time I try to open a network (samba) file in OpenOffice.org Writer or calc. However, when I have the same file on the local machine, it has no problems opening the file.

I tried uninstalling and reinstalling OOo from Synaptic—still crashes on opening some files (but not all files) from the network.

Uninstalled and reinstalled using the OOo download: 3.2.1; had to use gftp to download it; http would not save it.

Still having the problem with OOo 3.2.1 crashing on many files.

Workaround is to open readonly, then resave it. Cannot resave on top of the read only file , so it is a two step process.

Is Ubuntu 10.04 incompatible with OOo 3.2?

Anybody got any ideas?

Thanks!

I just tested this between my HP netbook running lucid and my samba server. I was able to access OO files without problems, edit them and save them. OO on Lucid is 3.2. My samba sever is Mandriva 2010.1. The samba server version is 3.5.3 on Mandy. My server is hard wired to my router, and Lucid is a wireless connection.

So, I would have to say OO 3.2 is working as expected for me.

Just a suggestion, try starting OO from the command line. Sometimes a program will report errors on exit and leave them for you to see. It might give you a clew as to what the issue is. Log are a possibility also.

The advice, all over the 'net is not to "upgrade" (it sometimes / always breaks something ) but to save your personal files (I just make an external backup of ALL of /home), then do a clean install, then restore your personal data.

After that, I think you'll find everything works as well as it should.

I recently moved from 8.04 to 10.04. The above procedure worked, Oo-whatever included.

camorri--

I googled OOo crashes opening file, and found this bug report: https://bugs.launchpad.net/ubuntu/+s...rg/+bug/578402

I tried the solution/workaround that someone there posted, mounting cifs with the switch nobrl, and have been working all afternoon with no problems, so for me it seems to be a fix.

When I put this switch in fstab and then umount and mount -a, "nobrl" does not show up in mount -l, but it does seem to make a difference.

Thanks for checking it out on your machine. Perhaps yours had that command already, or perhaps mine had something in it that nobrl overrides.

tredegar--

I thought of a clean install, and was near ready to try it. But I am finding through this exercises that I have a lot of tweaks in place (such as bookmarks in firefox, email addresses and my own email account preferences and signatures in evo, special key combinations in OOo, and I am sure lots more all over the place, that I suspect it might have been a bigger pain to start from scratch. Although it would have cleared some deadwood, too!

It still is something I may do in the future, or with another of my machines.

Thanks, tredegar!

Interesting, I read the entire bug report. I mounted the share via Nautilus, and it is reported that worked for other users. Hmmm. Glad you found a fix, 'nobrl' in the mount. And a big thank-you for updating the thread with a fix.

camorri--

Thanks!

And as to updating the thread: I seldom have answers to anybody else's issues, but I figure this is a way I can add to the sum total of the knowledge of Linux users, by posting what answers or workarounds I have found for my problems. Bread crumbs all over the place can help the lost find their way!

Thanks for encouraging me!

Have you tried opening the OOo files on the NAS as root instead of an average user? That might also be a workaround to the bug. To open the NAS mount point as root (via Alt+F2, not the terminal):

Kenny--

No I have not done that.

Interesting. Did not know Alt+F2 acted differently from terminal. Does it automatically have su privileges, or do something else?

In any case, I do not know what an NAS is, even after looking at the wikipedia article on it. Sounds kind of like a dumb server. I have a regular server.

Anyway, I tried your command, and it seemed to install a whole new instance of OOo on my computer--ran through a new welcome screen and all. But it did open a file that had been problematic, so your way might be a clue. I would not want to mount these volumes as root as a regular practice, though.

So what have we learned?