[Libreoffice-bugs] [Bug 98343] FILEOPEN: can't open files in path of more than 260 chars

2018-12-14 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=98343

Mike Kaganski  changed:

   What|Removed |Added

   Assignee|libreoffice-b...@lists.free |mikekagan...@hotmail.com
   |desktop.org |
 Status|NEW |ASSIGNED

--- Comment #18 from Mike Kaganski  ---
https://gerrit.libreoffice.org/65158

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[Libreoffice-bugs] [Bug 98343] FILEOPEN: can't open files in path of more than 260 chars

2018-12-14 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=98343

--- Comment #17 from Eneko Lacunza  ---
I don't have a build environment to build and test modified binaries; but can
test if someone can produce those...

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[Libreoffice-bugs] [Bug 98343] FILEOPEN: can't open files in path of more than 260 chars

2018-12-13 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=98343

--- Comment #16 from Aron Budea  ---
Thanks for retesting, Eneko. I still couldn't figure out what else it depends
on, because for me for long paths the path segments are substituted with their
8.3 variant, which doesn't cause an error.

Comment 5 from V Stuart gave me a hint, though, and I tried with LO dialogs.
The setting can currently be found in expert configuration: set
UseSystemFileDialog to false.
With that I can simply reproduce this bug by navigating a long Windows share
path. Getting to a level too deep gives the same error, with the share's first
character being cut off.

himajin10's code pointer is also spot on, this line is copying the path
incorrectly, cutting off the first character:
rtl_uString_newFromStr_WithLength( , aBuf + 2, nNewLen - 2 );
https://opengrok.libreoffice.org/xref/core/sal/osl/w32/file_url.cxx?r=ab9b67bb#699

However, the problem might actually be in GetCaseCorrectPathName(...) call,
which cuts starting "" (technically two backslashes) to "\\" (a single
backslash), if this wasn't the case, the previously mentioned code would be
fine:
https://opengrok.libreoffice.org/xref/core/sal/osl/w32/file_url.cxx?r=ab9b67bb#682

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[Libreoffice-bugs] [Bug 98343] FILEOPEN: can't open files in path of more than 260 chars

2018-12-10 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=98343

--- Comment #15 from Eneko Lacunza  ---
I tried with LibreOffice 5.2 and also with 6.1.3.2 x64, and continue to
reproduce the issue on Windows 2012r2 (dind't test in other systems).

I have tried clicking from Windows file manager and also from LibreOffice's
open dialog.

Windows is Spanish / Spain.

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[Libreoffice-bugs] [Bug 98343] FILEOPEN: can't open files in path of more than 260 chars

2018-12-06 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=98343

--- Comment #14 from Aron Budea  ---
I tried reproducing this again, but for some reason now the long path elements
are replaced with an 8.3 shortened version, and the bug doesn't occur. Eg. in a
path similar to comment 8's, "4 PRODUCCIÓN" becomes "4PRODU~1".

Surely this depends on something else as well, I wonder what.

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[Libreoffice-bugs] [Bug 98343] FILEOPEN: can't open files in path of more than 260 chars

2018-09-06 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=98343

--- Comment #13 from himajin100...@gmail.com ---
https://opengrok.libreoffice.org/xref/core/sal/osl/w32/file_url.cxx?r=e6f4779d#701
https://opengrok.libreoffice.org/xref/core/sal/osl/w32/file_url.cxx?r=e6f4779d#713

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[Libreoffice-bugs] [Bug 98343] FILEOPEN: can't open files in path of more than 260 chars

2017-09-13 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=98343

Aron Budea  changed:

   What|Removed |Added

 Status|UNCONFIRMED |NEW
 Ever confirmed|0   |1

--- Comment #12 from Aron Budea  ---
Reproduced using a 6.0 daily build (2017-09-11_06:28:48,
ffeb750163909e15ee0dd2d16f8030bf08e66eae).

It has to be a network share, for local paths it seems to work, right?

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[Libreoffice-bugs] [Bug 98343] FILEOPEN: can't open files in path of more than 260 chars

2017-09-09 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=98343

Dieter Praas  changed:

   What|Removed |Added

 CC||dgp-m...@gmx.de
 Blocks||109530


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=109530
[Bug 109530] [META] File opening issues
-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[Libreoffice-bugs] [Bug 98343] FILEOPEN: can't open files in path of more than 260 chars

2016-10-13 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=98343

--- Comment #11 from Eneko Lacunza  ---
Just tested with 5.2.2.2 x86 and issue persists.

Thanks

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[Libreoffice-bugs] [Bug 98343] FILEOPEN: can't open files in path of more than 260 chars

2016-10-10 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=98343

tommy27  changed:

   What|Removed |Added

 CC||ba...@quipo.it

--- Comment #10 from tommy27  ---
please retest with LibO 5.1.5 or 5.2.2 and tell if issue persists

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[Libreoffice-bugs] [Bug 98343] FILEOPEN: can't open files in path of more than 260 chars

2016-03-11 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=98343

--- Comment #9 from Eneko Lacunza  ---
I tried to open this very file with notepad from Windows explorer and works
perfectly (garbage shown though ;) ).

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[Libreoffice-bugs] [Bug 98343] FILEOPEN: can't open files in path of more than 260 chars

2016-03-11 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=98343

--- Comment #8 from Eneko Lacunza  ---
Created attachment 123490
  --> https://bugs.documentfoundation.org/attachment.cgi?id=123490=edit
Error window

Correct path should be:
\\SERVAGURAIN1\agurain-urretxu\testlibreofficebug\SISTEMA CALIDAD\Sistema
integrado pruebalibreoffice XX.xX.12\4 PRODUCCIÓN\7.5. TRAZABILIDAD Y RETIRADA
PRODUCTO\Simulacro retirada de producto\libreoffice test\Acta Comite de crisis 
Simulacro 01.01.2015.odt

OR in unicode:
\\?\UNC\SERVAGURAIN1\agurain-urretxu\testlibreofficebug\SISTEMA CALIDAD\Sistema
integrado pruebalibreoffice XX.xX.12\4 PRODUCCIÓN\7.5. TRAZABILIDAD Y RETIRADA
PRODUCTO\Simulacro retirada de producto\libreoffice test\Acta Comite de crisis 
Simulacro 01.01.2015.odt

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[Libreoffice-bugs] [Bug 98343] FILEOPEN: can't open files in path of more than 260 chars

2016-03-11 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=98343

--- Comment #7 from raal  ---
(In reply to Eneko Lacunza from comment #6)
> Windows can in fact use PATHs longer than 260 chars, using unicode paths,
> and LO is trying to use them (they start with "\\?\"). Problem is first
> server char is lost.
> 
> Error message shows path starting "\\?\UNC\erver\..." but it is wrong,
> should be "\\?\UNC\server\..."
> 


Could you attach error message and write full correct path?

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[Libreoffice-bugs] [Bug 98343] FILEOPEN: can't open files in path of more than 260 chars

2016-03-11 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=98343

--- Comment #6 from Eneko Lacunza  ---
Windows can in fact use PATHs longer than 260 chars, using unicode paths, and
LO is trying to use them (they start with "\\?\"). Problem is first server char
is lost.

Error message shows path starting "\\?\UNC\erver\..." but it is wrong, should
be "\\?\UNC\server\..."

Build details:
---
Versión: 5.0.5.2
Id. de compilación: 55b006a02d247b5f7215fc6ea0fde844b30035b3
Configuración regional: es-ES (es_ES)
---

It was the Windows OS explorer dialog, but I tried with LibreOffice dialog as
per your instructions, and the same error appears.

I can see path has one non-ascii char (Ó), maybe that's the problem?. I tested
putting more non-ascii chars in the file name, but the same error remains (no
difference in lost chars in server name)

Thanks

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[Libreoffice-bugs] [Bug 98343] FILEOPEN: can't open files in path of more than 260 chars

2016-03-10 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=98343

V Stuart Foote  changed:

   What|Removed |Added

 CC||vstuart.fo...@utsa.edu

--- Comment #5 from V Stuart Foote  ---
(In reply to Eneko Lacunza from comment #0)
> This problem happens double-click on Windows file explorer, and also using
> the Open File dialog inside Writer. Tested using a Windows share.
> 

Was that the OS Windows explorer dialog, or had you enabled internal
LibreOffice Open/Save dialogs from Tools -> Options -> General:  checkbox "Use
LibreOffice Dialogs"

Also, build details for the LibreOffice install? Simply clip from the Help ->
About LibreOffice dialog.

Thanks.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[Libreoffice-bugs] [Bug 98343] FILEOPEN: can't open files in path of more than 260 chars

2016-03-10 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=98343

raal  changed:

   What|Removed |Added

 CC||r...@post.cz

--- Comment #4 from raal  ---
https://msdn.microsoft.com/en-us/library/aa365247%28VS.85%29.aspx
Maximum Path Length Limitation
In the Windows API (with some exceptions discussed in the following
paragraphs), the maximum length for a path is MAX_PATH, which is defined as 260
characters.

Not sure if LO's bug, for example I can not copy file into directory long path
with Windows Explorer (win7).

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[Libreoffice-bugs] [Bug 98343] FILEOPEN: can't open files in path of more than 260 chars

2016-03-10 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=98343

--- Comment #3 from Eneko Lacunza  ---
Yes, I tried with Adobe Acrobat for example; no problems.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[Libreoffice-bugs] [Bug 98343] FILEOPEN: can't open files in path of more than 260 chars

2016-03-10 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=98343

Buovjaga  changed:

   What|Removed |Added

 CC||todven...@suomi24.fi

--- Comment #2 from Buovjaga  ---
Other software are able to open such files?

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[Libreoffice-bugs] [Bug 98343] FILEOPEN: can't open files in path of more than 260 chars

2016-03-02 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=98343

--- Comment #1 from Eneko Lacunza  ---
We tested on Windows 7 Pro 64 bits and Windows Server 2012r2 Std 64bits.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs