Prev: Unable to start tightvncserver
Next: console resolution
From: Patrick Wiseman on 22 Jan 2010 11:00
On Fri, Dec 4, 2009 at 9:21 AM, Patrick Wiseman <pwiseman(a)gmail.com> wrote:
> Updating my testing system this morning, I noticed that OpenOffice was
> being upgraded, so I shut down my open spreadsheet.  When configuring
> openoffice.org-writer2latex, aptitude complained "OpenOffice.org is
> running right now. This can cause problems with (de-)registration of
> components and extensions.  You should close all running instances of
> OpenOffice.org (including any currently running Quickstarter) before
> proceeding with the package upgrade."  So I opened a root terminal,
> did 'ps aux | grep office', found soffice.bin running, killed it, and
> proceeded.  A little later, aptitude complained again of
> OpenOffice.org running.  As I was watching the upgrade output, I saw
> docvert REstart OpenOffice, so that soffice.bin was running again!  I
> killed it again and the upgrade proceeded without further incident.
>
> I've submitted a bug report against docvert (there being some 32
> packages associated with OO.o!!  I knew it was bloatware, but 32?!)
> This is just FYI should someone else encounter the same issue.

Yesterday, six weeks later, it happened again.

Patrick


--
To UNSUBSCRIBE, email to debian-user-REQUEST(a)lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster(a)lists.debian.org
 | 
Pages: 1
Prev: Unable to start tightvncserver
Next: console resolution