[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#444783: marked as done (openoffice.org: delay exit when openning file in already-running OOo instance)

Your message dated Wed, 27 Feb 2008 01:42:24 +0200
with message-id <47C4A3E0.5040402@debian.org>
and subject line Re: Bug#444783: The 2nd Debian Openoffice.org bug triage - bug #444783
has caused the Debian Bug report #444783,
regarding openoffice.org: delay exit when openning file in already-running OOo instance
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
444783: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=444783
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: openoffice.org
Version: 2.0.4.dfsg.2-7etch2
Severity: wishlist

Currently, if openoffice is already running, and new 'oowriter file.odt' or
similar command is executed, it just asks already running OOo to open the file,
and then exits.

This behaviour is not friendly to e.g. mail clients that use oowirter to
show attachments. Usual behaviour of mail client is: same attachment to
a temporary file, then run command, then wait for command to exit, then
remove temporary file. With current openoffice behaviou, file removal in
this scenario may happen (and really usually happens) faster that running
OOo will open it. This resultis in unpleasant user experience - user
clicks on attachment and gets an error message that some file under /tmp
does not exist.

Although this may be workaroundable by configuring mail clent to run not
OOo itself but a wrapper that will run OOo and then sleep for some
seconds, problem does exist it default setup (e.g. kmail + OOo), and (as
mentioned above) results in unpleasant user experience.

It would be better if OOo will not exit immediately after telling
running instance to open the file, but instead will wait until that file
is closed. Something similar to 'vim --remote-wait-silent'.


-- System Information:
Debian Release: 4.0
  APT prefers stable
  APT policy: (640, 'stable'), (620, 'testing'), (600, 'unstable'), (550, 'experimental')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18-5-k7
Locale: LANG=ru_RU.KOI8-R, LC_CTYPE=ru_RU.KOI8-R (charmap=KOI8-R)

Versions of packages openoffice.org depends on:
ii  openoffice.org-base  2.0.4.dfsg.2-7etch2 OpenOffice.org office suite - data
ii  openoffice.org-calc  2.0.4.dfsg.2-7etch2 OpenOffice.org office suite - spre
ii  openoffice.org-core  2.0.4.dfsg.2-7etch2 OpenOffice.org office suite archit
ii  openoffice.org-draw  2.0.4.dfsg.2-7etch2 OpenOffice.org office suite - draw
ii  openoffice.org-impre 2.0.4.dfsg.2-7etch2 OpenOffice.org office suite - pres
ii  openoffice.org-java- 2.0.4.dfsg.2-7etch2 OpenOffice.org office suite Java s
ii  openoffice.org-math  2.0.4.dfsg.2-7etch2 OpenOffice.org office suite - equa
ii  openoffice.org-write 2.0.4.dfsg.2-7etch2 OpenOffice.org office suite - word

openoffice.org recommends no packages.

-- no debconf information

--- End Message ---
--- Begin Message --- 
Version: 1:2.3.1-3

Nikita V. Youshchenko wrote:
> notfound 444783 1:2.3.1-2~bpo40+1
> thanks
> 
> This but does not reproduce on OOo 1:2.3.1-2~bpo40+1 which I have currently 
> install on my etch system.

Closing than...

-- 
Lior Kaplan
kaplan@debian.org

GPG fingerprint:
C644 D0B3 92F4 8FE4 4662  B541 1558 9445 99E8 1DA0

--- End Message ---
Reply to: