Bug 58903 - Incorrect handling of file open from Mac OS X Finder with multiple files
Summary: Incorrect handling of file open from Mac OS X Finder with multiple files
Status: RESOLVED DUPLICATE of bug 56857
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
3.6.4.3 release
Hardware: IA64 (Itanium) macOS (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-12-31 11:26 UTC by Kent Damgaard
Modified: 2012-12-31 14:21 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:

Attachments
Screen shot of error message (108.57 KB, image/png)
2012-12-31 11:27 UTC, Kent Damgaard 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Kent Damgaard 2012-12-31 11:26:03 UTC 
In the OS X Finder, select multiple documents, then from the right-click menu select "Open with ..." and select LibreOffice.

The result is an error message that the files do not exist instead of them being opened (see attached screenshot).

If only a single file is selected, it will be opened correctly without problems. All three files will open without problem is selected one by one. They will also open if double-clicked, as long as it is only a single document.

The problem seems to be specific to OS X, and is seen on OS X 10.8.2, but I believe it also was there on Snow Leopard.
Comment 1 Kent Damgaard 2012-12-31 11:27:07 UTC 
Created attachment 72337 [details]
Screen shot of error message
Comment 2 Jorendc 2012-12-31 13:45:49 UTC 
Thanks for reporting!

I can reproduce using LO 4.1 and LO 3.6.4.3. Same error message as attached by Kent (bug reporter).

Tested with Mac OSX 10.8.2

Kind regards,
Joren
Comment 3 Alex Thurgood 2012-12-31 13:55:24 UTC 
This is a duplicate bug report.

*** This bug has been marked as a duplicate of bug 56857 ***
Comment 4 Kent Damgaard 2012-12-31 14:21:51 UTC 
Tried searching, but did not find the original bug.

Thanks guys. Happy new  year :)