Launching with Nautilus double-click unreliable without Quickstarter? - Karmic / openoffice.org 1:3.1.1-5ubuntu1

I guess the opening time in OO depends on your computers as well, it
won't necessarily be the problem from within nautilus. But if you open
OO by itself it takes less memory then it would load properly as
compared to using nautilus

--
Regards,
Vikram Dhillon

On Tue, 2009-12-08 at 00:14 +0000, floid wrote:
> New question #93255 on openoffice.org in ubuntu:
> https://answers.launchpad.net/ubuntu/+source/openoffice.org/+question/93255
>
> This should probably be a bug, but I might as well ask an "Is it just me?" first, given the time I'd have to spend collecting information to file a useful bug report -
>
> As described in another question, I recently upgraded some office machines to Ubuntu 9.10 from 6.06 and 8.04, respectively (the long way- that's a lot of cdromupgrades to sit through, but 6.06 was getting real long in the tooth!), and pushed a bunch of data off what had been the 6.06 machine onto a NFS mount.
>
> Previously, the 6.06 box - my workstation - had the data locally and the 8.04 machine was NFS mounting from it. Both machines had been running with the OO.o quickstarter for ages and no problems loading documents through Nautilus were observed. The new setup has moved the data and nfsd to a DragonFly BSD-based server, and the NFS mount(s) appear to be functioning reliably with anything I can throw at them from the command line.
>
> ...
>
> After the upgrades, my workstation happened to come up with the Quickstarter disabled, and I "rapidly" discovered that double-clicking to open an OO.o document in Nautilus could be very hit-or-miss; sometimes I would "get lucky," but more often OO.o would display its borderless splash window and then hang at the end of its progress bar.
>
> Oddly, however, a OO.o session opened with no document would "just work," and use of File->Open within that session would then work with no hang-ups.
>
> Similarly, with OO.o made resident through the quickstarter (which I intended to run anyway), I have had no trouble since, and given that, I have to file this under "things I have no time to debug further myself." But it definitely deserves documentation, which filing this "question" might provide.
>
> ...
>
> Unfortunately, I didn't check whether launching OO.o through Nautilus for files stored locally would fare better, as all my documents of interest were on the NFS mount.
>
> ...
>
>
> So, yeah, this is another one where the question is "Has anyone else noticed this?" / Did a Nautilus update already specifically fix it?
> And if you have, but haven't hit on running the Quickstarter or opening OO.o without a file argument through the Applications menu or command line, does that solve the behavior for you?
>

Thanks for your thoughts. It was definitely a hang rather than a load-time issue, but I should've paid attention to the state the process wound up in. If it were as simple as not having the Quickstarter up, I just realized I "should" be able to reproduce it on my home machine and can't - but on further reflection that's also a different arch (64-bit at home, 32-bit at the office), so I haven't proved much of anything.

I should really poke at it more and see if it's only an issue on the NFS mount, and if it is, if the same thing turns up Linux-to-Linux between the two workstations. Unfortunately I need to return to getting some "actual" work done (and finishing more pressing administrative tasks with that setup, for that matter). So the best I can do is document "This happened and it was weird."

As far as memory, the office machines have 1GB, and mine certainly wasn't swapping, just the process stalling out for some reason I didn't complete due diligence on. :)