Ask Your Question
0

LibreOffice 3.6.1 let Explorer.exe crash [closed]

asked 2012-09-30 16:47:54 +0200

Willem gravatar image

updated 2015-10-18 04:13:27 +0200

Alex Kemp gravatar image

After installing version 3.6.1 on a brand new Intel Core i5-3317U processor, win7 home premium 64 bit, computer after a few hours the explorer start to stop working. I found out that LibreOffice 3.6.1 was the cause. The story: The microsoft solution was a automatical restart of the explorer but in a short time (few second) it stops again, etc etc. went back to the original setup, but after installing again all my programs the problem suddenly come back. It was very difficult, because all I want to do has to do with the Explorer (at least a window) and also that window was first blocked when the explore stops, and exit during the restart of the explorer. By quick pressing the right buttons I was after a long time able to stop the system. Also in the save-mode the same happen. I was lucky to have a second account and that was stil working normal. There I could look-up the fault and found this:

Logboeknaam:   Application
Bron:          Application Error
Datum:         30-9-2012 0:05:10
Gebeurtenis-id:1000
Taakcategorie: (100)
Niveau:        Fout
Trefwoorden:   Klassiek
Gebruiker:     n.v.t.
Computer:      Ultra-Willem
Beschrijving:
Naam van toepassing met fout: explorer.exe, versie: 6.1.7601.17567, tijdstempel: 0x4d672ee4
Naam van module met fout: shlxthdl_x64.dll, versie: 3.6.1.2, tijdstempel: 0x5034bc94
Uitzonderingscode: 0xc0000005
Foutoffset: 0x000000000001b1bf
Id van proces met fout: 0x4b4
Starttijd van toepassing met fout: 0x01cd9e8e74b873c2
Pad naar toepassing met fout: C:\Windows\explorer.exe
Pad naar module met fout: C:\Program Files (x86)\LibreOffice 3.6\program\shlxthdl\shlxthdl_x64.dll
Rapport-id: bbaefd54-0a81-11e2-96df-bbfdba152009
Gebeurtenis-XML:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Application Error" />
    <EventID Qualifiers="0">1000</EventID>
    <Level>2</Level>
    <Task>100</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2012-09-29T22:05:10.000000000Z" />
    <EventRecordID>2814</EventRecordID>
    <Channel>Application</Channel>
    <Computer>Ultra-Willem</Computer>
    <Security />
  </System>
  <EventData>
    <Data>explorer.exe</Data>
    <Data>6.1.7601.17567</Data>
    <Data>4d672ee4</Data>
    <Data>shlxthdl_x64.dll</Data>
    <Data>3.6.1.2</Data>
    <Data>5034bc94</Data>
    <Data>c0000005</Data>
    <Data>000000000001b1bf</Data>
    <Data>4b4</Data>
    <Data>01cd9e8e74b873c2</Data>
    <Data>C:\Windows\explorer.exe</Data>
    <Data>C:\Program Files (x86)\LibreOffice 3.6\program\shlxthdl\shlxthdl_x64.dll</Data>
    <Data>bbaefd54-0a81-11e2-96df-bbfdba152009</Data>
  </EventData>
</Event>

Removing LibreOffice under the second account was possible and the problem was solved. I now use the portable version without problems. What I have ... (more)

edit retag flag offensive reopen merge delete

Closed for the following reason the question is answered, right answer was accepted by Alex Kemp
close date 2015-10-18 04:14:00.198129

Comments

Another pc with win7 32bit just start to show the same problem but now was the fault modul C:\Program Files\LibreOffice 3.6\program\shlxthdl\shlxthdl.dll. There will be a lot of disappointed users of LO,(if they found out that LO was the cause, which is difficult to detect..)

Willem gravatar imageWillem ( 2012-10-01 17:18:07 +0200 )edit

4 Answers

Sort by » oldest newest most voted
1

answered 2012-10-01 05:20:36 +0200

JohnD gravatar image

This sounds a lot like a number of bugs that have been reported on 3.6.1 and Windows Explorer. The interim solution seems to be to install LO 3.6.1 in custom mode and un-select the option add-on for Windows Explorer integration.

I believe this problem, and similar ones, are being corrected for 3.6.2 which is due for release within the next couple of weeks.

edit flag offensive delete link more

Comments

manj_k gravatar imagemanj_k ( 2012-10-01 06:22:22 +0200 )edit

Thanks John. For me it is solved sofar. I hope not too much people try to install LO on win7 64 bit machines, because for most it will not be clear LO installation was the problem maker!.

Willem gravatar imageWillem ( 2012-10-01 13:39:08 +0200 )edit
0

answered 2012-09-30 19:37:25 +0200

Willem gravatar image

It could not be the user account I think because LO was not open by that account or by the other. Could it have to do with update checking on the background or something like that? Could it be that it is only done under the account where LO was installed? could it be perhaps a bug?

edit flag offensive delete link more

Comments

If a second user account worked fine than there was/is something in the original account causing the problem and LO triggered it. Is it possible that the quick launch utility the LO installs was running?

bllgvn gravatar imagebllgvn ( 2012-09-30 22:20:31 +0200 )edit

Thanks for your suggestion but it proofed to be a bug. See later comments with links.

Willem gravatar imageWillem ( 2012-10-01 20:14:27 +0200 )edit
0

answered 2012-09-30 18:34:23 +0200

bllgvn gravatar image

If LibreOffice is working in one user account and not another that follow the reset instructions at http://wiki.documentfoundation.org/UserProfile

edit flag offensive delete link more

Comments

Thanks for your suggestion but it proofed to be a bug. See later comments with their links.

Willem gravatar imageWillem ( 2012-10-01 20:13:10 +0200 )edit
0

answered 2012-09-30 22:27:37 +0200

Willem gravatar image

updated 2012-10-01 21:14:13 +0200

I found a bug report on this mather. See

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

edit flag offensive delete link more

Comments

According to the report the status of the bug is resolve as of 3.6.1 and the early development stages of 3.7.0, if you think the is what is responsible for what you are experiencing than I would suggest confirming the version of your software and update as needed

bllgvn gravatar imagebllgvn ( 2012-10-01 03:32:21 +0200 )edit

As you look near the end of the bug report comments you will see that the bug was not fixed by re-annouce the dll, but the last comment give a work around the problem by during installing 3.6.1 skip the installation of explorer support (no explorer add-on put on the system). Thus not solved!!!

Willem gravatar imageWillem ( 2012-10-01 11:48:13 +0200 )edit

Perhaps the microsoft safety update for the explorer, a few days ago could have an influence on the occuring of the error.

Willem gravatar imageWillem ( 2012-10-02 09:57:34 +0200 )edit

Question Tools

Stats

Asked: 2012-09-30 16:47:54 +0200

Seen: 1,760 times

Last updated: Oct 01 '12