[Libreoffice-bugs] [Bug 52276] New: .odt or .fodt file causes Windows Explorer (Windows 7) to crash and restart

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=52276

             Bug #: 52276
           Summary: .odt or .fodt file causes Windows Explorer (Windows 7)
                    to crash and restart
    Classification: Unclassified
           Product: LibreOffice
           Version: 3.6.0.1 rc
          Platform: Other
        OS/Version: Windows (All)
            Status: UNCONFIRMED
          Severity: critical
          Priority: medium
         Component: Libreoffice
        AssignedTo: libreoffice-bugs at lists.freedesktop.org
        ReportedBy: bugs at eikota.de


It is very likely that the following is either not reproducible or NOTOURBUG.
Nevertheless I have to report it, because there is at least a minimal chance
that this is a bug in LibreOffice; and if it is our bug, it is an important
one. So I report it, and ask our Windows expert (I'm no one) to investigate if
this is really a LibreOffice issue or not reproducible or just NOTOURBUG. Thank
you!

I just installed LibreOffice 3.6.0.1 (= RC 1) on a laptop with Windows 7
Professional which I borrowed from a friend. There was no LibreOffice (or OOo
or AOO) installed on this machine before, but MS Office Professional 2010.
Installation of LibO and of the German helppack worked fine. Then I started
LibreOffice, changed only the most important application settings (options),
and created a new Writer file with a single line of text in the default style.
I saved this file first in .odt format and then in .fodt format, both on the
desktop, named "Test.odt" and "Test.fodt".

After quitting LibreOffice (which made Windows Explorer come to the front) the
horror started: Windows Explorer was quit and restarted again and again, every
time showing only the same generic alert ("Windows Explorer has encountered an
error and must restart" or so). Even restarting the complete machine did not
have any effect: as soon as the desktop became visible, the Explorer restart
loop began again.

When I logged in as admin, the Explorer worked again (because the files where
not visible on the admin desktop); but as soon as I navigated with Explorer to
the main user's "Desktop" folder, opened it and clicked once (!) on one of the
files (I forgot on which one first, sorry!) to select it, Windows Explorer
crashed again with the same message.

This indicates that the problem must have involved one (or both?) of my
"Test.odt" and "Test.fodt" files. This is affirmed by the following: after
deleting both files from the desktop via a complicated "telepathic" action, the
problem went away for good. Which one of the two files was the reason I can not
tell. I can just say that for the .odt file the Win Explorer showed the correct
(LibreOffice .odt) icon, and for the .fodt the Explorer showed a preview, which
was correct, too (a blank page with a single line of text).

Now I know that this looks like NOTOURBUG -- I would think that one or both of
the files exhibited a bug somewhere deep in Windows Explorer. But I don't know
enough about Windows to judge this issue. Are there any file viewer extensions
or so which LibreOffice installs on Windows? Then the bug could be somewhere in
that extensions. Or is it possible that this is a conflict about registered
file types (as said above, MS Office Professional 2010 is installed on the
machine)?

I'm sorry that I can't do any additional testing, because this was not *my*
machine and I can't do critical things on it :-( So I ask our Windows experts
to investigate this. However, do NOT save any test files on the desktop,
because this will (if you can reproduce the issue) cause the same horrific and
endless Explorer restart loop; save the files into a folder/directory
somewhere, and delete them (if necessary) by terminal commands ("cd ..." to the
directory in question, then "dir", then "del ...").

-- 
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.