Re: [libreoffice-users] Re: Sun dll shlxthdl and windows explorer.execrash

2012-09-02 Thread Heikki Jussila
Hi,
thanks for the bug link. I'll try it later, but now I have to slow
connection to download 3.6.1.2 and to what you suggested. I wonder if the
missing JAVA JRE was somehow a reason, since if LO/AOO/OOo leaves into
windows registry something that windows thinks it has this function within
the program in question (in this case LO). This means that if you have e.g.
JAVA installed and it is needed by some program to function properly, it
should be said clearly that the user should NOT unistall that helper (even
though it might cause security issues as JAVA does).

Oh, well will  try and come back to this thread when I have been able to do
all the necessary backups so that it do not loose stuff if something really
nasty happens. Better always keep it safe, since I started using computers
in early 1970's and I have always liked the idea to have a backup, even of
punchcards (which you could misplace!)

Heikki Jussila
freelance researcher and geographer

On 1 September 2012 02:04, V Stuart Foote vstuart.fo...@utsa.edu wrote:

 Dave,

 Sorry to hear that. You should consider reopening
 https://bugs.freedesktop.org/show_bug.cgi?id=53533 and providing your
 details there.

 Also, while it is a hassle, back out LibO 3.6.1.2 deleting per-user
 profiles. Then reinstall selecting a Custom installation. Deselect the
 Windows Explorer extension and allow the installation to proceed. See if
 that clears your issues with ODF--and if you do reopen the bug, add
 those details to it.

 Stuart



 -Original Message-
 From: Dave Barton [mailto:d...@tasit.net]
 Sent: Friday, August 31, 2012 6:00 PM
 To: users@global.libreoffice.org
 Subject: Re: [libreoffice-users] Re: Sun dll shlxthdl and windows
 explorer.execrash

 V Stuart Foote wrote:
  Probably related to the LibreOffice's Windows Explorer extension
 
  Most issues fixed with 3.6.1 build.
 
  Ref these bugzilla reports:
 
  https://bugs.freedesktop.org/show_bug.cgi?id=52078
  https://bugs.freedesktop.org/show_bug.cgi?id=53533
 
  Install a current Java JRE and LO 3.6.1 and should resolve.
 
  Stuart


 Unfortunately, this is not the solution. LO Version 3.6.1.2 (Build ID:
 e29a214) still kills Windows Explorer when the mouse is hovered over
 some ODF file names. It make no difference if Java is installed or not.

 Dave



 --
 For unsubscribe instructions e-mail to: users+h...@global.libreoffice.org
 Problems?
 http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
 Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
 List archive: http://listarchives.libreoffice.org/global/users/
 All messages sent to this list will be publicly archived and cannot be
 deleted



-- 
For unsubscribe instructions e-mail to: users+h...@global.libreoffice.org
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/users/
All messages sent to this list will be publicly archived and cannot be deleted


[libreoffice-users] Re: Sun dll shlxthdl and windows explorer.execrash

2012-09-02 Thread V Stuart Foote
Heikki,

Recent work on the LibO Windows Explorer extension (shlxthdl.dll) has caused
the issue reported in referenced bugs.  And is probably not at all related
to the the Sun/Oracle JRE in use.

Reinstall the 3.6.1.2 after your backup and uninstall. But this time perform
a custom installation and uncheck the Windows Explorer extension.  The
shlxthdl folder and the .dll will not even be installed.

Clearing off all your Sun/Oracle Java Runtime Environments, and then
installing just a single current Oracle JRE is really just routine
maintenance that will result in a more stable Windows system.

Stuart



--
View this message in context: 
http://nabble.documentfoundation.org/Sun-dll-shlxthdl-and-windows-explorer-exe-crash-tp4004653p4005066.html
Sent from the Users mailing list archive at Nabble.com.

-- 
For unsubscribe instructions e-mail to: users+h...@global.libreoffice.org
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/users/
All messages sent to this list will be publicly archived and cannot be deleted



RE: [libreoffice-users] Re: Sun dll shlxthdl and windows explorer.execrash

2012-08-31 Thread V Stuart Foote
Dave,

Sorry to hear that. You should consider reopening
https://bugs.freedesktop.org/show_bug.cgi?id=53533 and providing your
details there.

Also, while it is a hassle, back out LibO 3.6.1.2 deleting per-user
profiles. Then reinstall selecting a Custom installation. Deselect the
Windows Explorer extension and allow the installation to proceed. See if
that clears your issues with ODF--and if you do reopen the bug, add
those details to it.

Stuart



-Original Message-
From: Dave Barton [mailto:d...@tasit.net] 
Sent: Friday, August 31, 2012 6:00 PM
To: users@global.libreoffice.org
Subject: Re: [libreoffice-users] Re: Sun dll shlxthdl and windows
explorer.execrash

V Stuart Foote wrote:
 Probably related to the LibreOffice's Windows Explorer extension

 Most issues fixed with 3.6.1 build.

 Ref these bugzilla reports:

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

 Install a current Java JRE and LO 3.6.1 and should resolve.

 Stuart


Unfortunately, this is not the solution. LO Version 3.6.1.2 (Build ID:
e29a214) still kills Windows Explorer when the mouse is hovered over
some ODF file names. It make no difference if Java is installed or not.

Dave



-- 
For unsubscribe instructions e-mail to: users+h...@global.libreoffice.org
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/users/
All messages sent to this list will be publicly archived and cannot be deleted