https://bugs.documentfoundation.org/show_bug.cgi?id=158554
--- Comment #18 from Raúl Osuna ---
I can't reproduce it in GNU/Linux, btrfs FS:
Version: 7.6.4.1 (X86_64) / LibreOffice Community
Build ID: 60(Build:1)
CPU threads: 16; OS: Linux 6.6; UI render: default; VCL: kf5 (cairo+xcb)
Locale: es-
https://bugs.documentfoundation.org/show_bug.cgi?id=158554
--- Comment #17 from edg ---
(In reply to Mike Kaganski from comment #16)
> What is your file system BTW? Is it NTFS? Or maybe it is, say, ExFAT, by
> chance?
The file system is always NTFS.
The "username" part of the path was obviously
https://bugs.documentfoundation.org/show_bug.cgi?id=158554
--- Comment #16 from Mike Kaganski ---
What is your file system BTW? Is it NTFS? Or maybe it is, say, ExFAT, by
chance?
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.documentfoundation.org/show_bug.cgi?id=158554
--- Comment #15 from Mike Kaganski ---
Just in case: the path shown as problematic in comment 4 (and the one that I
used in comment 12) has total length of 260 characters (not including trailing
zero). This is already 1 character larger t
https://bugs.documentfoundation.org/show_bug.cgi?id=158554
--- Comment #14 from Mike Kaganski ---
(In reply to edg from comment #13)
On my test system, LongPathsEnabled exists and is 0 (zero).
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.documentfoundation.org/show_bug.cgi?id=158554
--- Comment #13 from edg ---
Probably the OS work in different ways.
Maybe in your system exist the registry value:
Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\FileSystem\LongPathsEnabled
(Type: REG_DWORD) and is set to
https://bugs.documentfoundation.org/show_bug.cgi?id=158554
--- Comment #12 from Mike Kaganski ---
(In reply to edg from comment #4)
> in this scenario (just one more character, 260, in the last level directory
> name where the document is present) the lock/samaphore remain in place after
> closin
https://bugs.documentfoundation.org/show_bug.cgi?id=158554
--- Comment #11 from Mike Kaganski ---
(In reply to edg from comment #8)
> > Recently there were Windows path fixes like ... bug 157820. ...
>
> It would be very nice if LO can support \\?\ unicode absolute path which
> heve not the 256
https://bugs.documentfoundation.org/show_bug.cgi?id=158554
--- Comment #10 from edg ---
(In reply to Buovjaga from comment #9)
> You don't happen to have any anti-virus software running that could meddle
> with the lock files?
No AV at all.
The lock files
Ex. .~lock.2023-12-21 - File not remov
https://bugs.documentfoundation.org/show_bug.cgi?id=158554
--- Comment #9 from Buovjaga ---
You don't happen to have any anti-virus software running that could meddle with
the lock files?
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.documentfoundation.org/show_bug.cgi?id=158554
--- Comment #8 from edg ---
(In reply to Buovjaga from comment #6)
> I don't reproduce this with
>
> Version: 7.6.4.1 (X86_64) / LibreOffice Community
> Build ID: e19e193f88cd6c0525a17fb7a176ed8e6a3e2aa1
> CPU threads: 2; OS: Windows 10.
https://bugs.documentfoundation.org/show_bug.cgi?id=158554
--- Comment #7 from Buovjaga ---
Oh, and a PowerShell tip for creating that long path:
New-Item -ItemType Directory 'z:\data\Enterprise name\customers\architecture,
constructions, buildings and materials\United States of
America\Missouri
https://bugs.documentfoundation.org/show_bug.cgi?id=158554
Buovjaga changed:
What|Removed |Added
CC||ilmari.lauhakangas@libreoff
https://bugs.documentfoundation.org/show_bug.cgi?id=158554
QA Administrators changed:
What|Removed |Added
Status|NEEDINFO|UNCONFIRMED
Ever confirm
https://bugs.documentfoundation.org/show_bug.cgi?id=158554
--- Comment #5 from QA Administrators ---
[Automated Action] NeedInfo-To-Unconfirmed
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.documentfoundation.org/show_bug.cgi?id=158554
--- Comment #4 from edg ---
in this scenario (259 total characters between drive letter, :, paths,
filename, . and extension) everything is ok and the lock/samaphore file is
removed:
C:\Users\Username\Documents\\lll\l
https://bugs.documentfoundation.org/show_bug.cgi?id=158554
--- Comment #3 from m.a.riosv ---
Can you test if there is a length limit, by changing the file name to a new
shorter one, or by modifying the length of the folder name?
--
You are receiving this mail because:
You are the assignee for t
https://bugs.documentfoundation.org/show_bug.cgi?id=158554
--- Comment #2 from edg ---
The files can be deleted in the usual way without making any particular
maneuver.
The strange thing is that if there is a path problem also the creation and the
modification of a document could be affected but
https://bugs.documentfoundation.org/show_bug.cgi?id=158554
m.a.riosv changed:
What|Removed |Added
CC||miguelangelrv@libreoffice.o
19 matches
Mail list logo