Back to bug 69066

Who When What Removed Added
momonasmon 2013-11-02 16:54:02 UTC CC chrisgriffinindy
momonasmon 2013-11-02 16:57:22 UTC Status UNCONFIRMED NEW
Component Libreoffice Installation
Version unspecified 4.1.1.2 release
Summary Upgrading LO gives notice about file in use Upgrading LO forces to close explorer.exe
Ever confirmed 0 1
kumara.bhikkhu 2013-11-05 06:52:15 UTC Priority medium high
CC kumara.bhikkhu
Whiteboard regression
kumara.bhikkhu 2013-11-05 06:53:20 UTC Summary Upgrading LO forces to close explorer.exe Upgrading LO requires user to terminate Explorer.exe on Windows
momonasmon 2013-11-08 08:23:11 UTC See Also https://bugs.freedesktop.org/show_bug.cgi?id=69043
mst.fdo 2013-12-02 19:04:02 UTC Keywords regression
CC mstahl, timar74
Whiteboard regression
rk662trc 2014-01-05 02:35:48 UTC Version 4.1.1.2 release 4.1.4.2 release
rk662trc 2014-01-05 02:48:04 UTC CC rk662trc
kumara.bhikkhu 2014-01-06 02:28:46 UTC Version 4.1.4.2 release 4.1.1.2 release
mst.fdo 2014-02-03 17:09:55 UTC See Also https://bugs.freedesktop.org/show_bug.cgi?id=56007
michael.meeks 2014-02-11 13:29:09 UTC Status NEW NEEDINFO
reg 2014-02-15 17:39:48 UTC CC reg
kumara.bhikkhu 2014-02-17 10:48:31 UTC Status NEEDINFO NEW
mst.fdo 2014-02-19 14:51:23 UTC Summary Upgrading LO requires user to terminate Explorer.exe on Windows Upgrading LO requires user to terminate Explorer.exe on Windows because of LO Explorer/Shell extensions
barta 2014-05-05 11:40:30 UTC See Also https://bugs.freedesktop.org/show_bug.cgi?id=78057
fios 2014-07-07 21:28:00 UTC CC fios
kumara.bhikkhu 2014-07-09 03:10:01 UTC Hardware x86-64 (AMD64) All
Whiteboard Workaround: Comment 12
qubit 2014-11-22 21:48:29 UTC CC qubit
Summary Upgrading LO requires user to terminate Explorer.exe on Windows because of LO Explorer/Shell extensions Upgrading LO requires user to terminate Explorer.exe on Windows because of LO Explorer/Shell extensions (Workaround: comment 12)
Whiteboard Workaround: Comment 12

Back to bug 69066

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.