Bug 113437 - [FILEOPEN,FILESAVE] Truncated error message for I/O error
Summary: [FILEOPEN,FILESAVE] Truncated error message for I/O error
Status: RESOLVED WORKSFORME
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
Version:
(earliest affected)
5.4.1.2 release
Hardware: All Linux (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-10-25 10:01 UTC by B.J. Herbison
Modified: 2019-07-09 14:30 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Attachments
Screen shot of the error message (10.72 KB, image/png)
2017-10-25 10:01 UTC, B.J. Herbison
Details

Note You need to log in before you can comment on or make changes to this bug.
Description B.J. Herbison 2017-10-25 10:01:00 UTC
Description:
I'm getting a truncated I/O error message. See the attachment.

This report is about the appearance of the error message, not the cause or usefulness of the message text.

This happened after an I/O problem with a file on a NAS device caused by switching from wired to wireless. (The device is still reachable so I'm not sure why there was an error. This connection problem happens occasionally.)

The attachment is from an open attempt. The message from the save attempt appeared the same.

Steps to Reproduce:
1. Modify a Calc file.
2. Switch from wired to wireless.
3. Try to save the file.
4. Restart Calc.
5. Try to open the file.


Actual Results:  
Any error messages are fully displayed, not truncated.

Expected Results:
In steps 3 and 5 a displayed error message was truncated.


Reproducible: Couldn't Reproduce

User Profile Reset: No

Additional Info:


User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:58.0) Gecko/20100101 Firefox/58.0
Comment 1 B.J. Herbison 2017-10-25 10:01:40 UTC
Created attachment 137280 [details]
Screen shot of the error message
Comment 2 B.J. Herbison 2017-10-27 11:06:22 UTC
The problem seems to be wrapping caused by the length of the file name. I reproduced the message with a shorter file name and the second line is "accessing <file name>."
Comment 3 Buovjaga 2017-11-09 12:03:32 UTC
This is with GTK3? You can see it from Help - About.
Comment 4 B.J. Herbison 2017-11-09 13:17:35 UTC
Yes, it is with GTK3.

The full string from Help About:

Version: 5.4.1.2
Build ID: 1:5.4.1-0ubuntu1
CPU threads: 8; OS: Linux 4.13; UI render: default; VCL: gtk3; 
Locale: en-US (en_US.UTF-8); Calc: group
Comment 5 Buovjaga 2017-11-09 16:01:09 UTC
It could be interesting to launch LibreOffice with some other backend than GTK3 and then reproduce the problem.

You can try launching from the command line:

SAL_USE_VCLPLUGIN=gen libreoffice
Comment 6 B.J. Herbison 2017-11-10 01:31:30 UTC
Using "SAL_USE_VCLPLUGIN=gen libreoffice" the message is still on three lines, but the message window is tall enough to see the full file name.

Version: 5.4.1.2
Build ID: 1:5.4.1-0ubuntu1
CPU threads: 8; OS: Linux 4.13; UI render: default; VCL: x11; 
Locale: en-US (en_US.UTF-8); Calc: group
Comment 7 Xisco Faulí 2018-11-27 12:57:03 UTC
Hello B.J. Herbison,
Could you please try to reproduce it with the latest version of LibreOffice
from https://www.libreoffice.org/download/libreoffice-fresh/ ?
I have set the bug's status to 'NEEDINFO'. Please change it back to
'UNCONFIRMED' if the bug is still present in the latest version.
Comment 8 B.J. Herbison 2018-12-14 17:28:13 UTC
I can't tell whether the truncation issue still exists. With 6.1.3.2 I have not been able to reproduce the error in six attempts with the Steps to Reproduce in .0.

As I noted in .0 the error only happen occasionally. Not being able to reproduce it now, a year later, could be an environmental change, a Ubuntu change, a Libreoffice change, or just good/bad luck in my attempts to reproduce it.
Comment 9 Xisco Faulí 2019-07-09 14:30:15 UTC
(In reply to B.J. Herbison from comment #8)
> I can't tell whether the truncation issue still exists. With 6.1.3.2 I have
> not been able to reproduce the error in six attempts with the Steps to
> Reproduce in .0.
> 
> As I noted in .0 the error only happen occasionally. Not being able to
> reproduce it now, a year later, could be an environmental change, a Ubuntu
> change, a Libreoffice change, or just good/bad luck in my attempts to
> reproduce it.

Thanks for retesting with the latest version.
Setting to RESOLVED WORKSFORME as the commit fixing this issue hasn't been identified.