Bug 57689 - FILEOPEN: xls file mistakenly imported as csv file
Summary: FILEOPEN: xls file mistakenly imported as csv file
Status: RESOLVED DUPLICATE of bug 53909
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
Version:
(earliest affected)
3.6.4.1 rc
Hardware: Other All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard: BSA
Keywords: regression
Depends on:
Blocks:
 
Reported: 2012-11-29 14:26 UTC by wvvelzen
Modified: 2012-11-30 11:45 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:

Attachments
xls file showing the false behaviour (6.00 KB, application/vnd.ms-excel)
2012-11-29 15:26 UTC, wvvelzen 		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 wvvelzen 2012-11-29 14:26:18 UTC 
See: http://ask.libreoffice.org/question/1755/xls-file-mistakenly-imported-as-csv-file/

Operating System: All
Last worked in: 3.5.4 release
Comment 1 wvvelzen 2012-11-29 15:26:23 UTC 
Created attachment 70796 [details]
xls file showing the false behaviour
Comment 2 Pedro 2012-11-29 16:55:59 UTC 
The bad news is that I can confirm that the sample file won't even open in LO 3.5.7.2 or 3.6.3.2 under Windows XP.
It fails with a General Error. General input/output error.

The good news is that it opens correctly using Version 4.0.0.0.alpha1+ (Build ID: 6aabe09ac092c51d4b394bde9c7ea0055b952e3)

My guess is that the I/O error is caused by the absence of Java in my machine (I will confirm it later on another PC)
Comment 3 Pedro 2012-11-29 23:55:13 UTC 
(In reply to comment #2)

> My guess is that the I/O error is caused by the absence of Java in my
> machine (I will confirm it later on another PC)

Apparently that is not the cause. Showed the same error on another PC with JRE 1.7.0_09 installed
Comment 4 Urmas 2012-11-30 00:04:07 UTC 

*** This bug has been marked as a duplicate of bug 53909 ***
Comment 5 wvvelzen 2012-11-30 11:45:38 UTC 
I can confirm this bug has been fixed. I tested this with the daily windows build for 3.6.4.3 .