Bug 51341

Summary: ERRORMESSAGE missing when trying to create folder with forbidden character
Product: LibreOffice Reporter: Rainer Bielefeld Retired <LibreOffice>
Component: UIAssignee: Not Assigned <libreoffice-bugs>
Status: RESOLVED INVALID    
Severity: normal CC: michael.meeks, serval2412
Priority: medium    
Version: 3.6.0.0.beta2   
Hardware: Other   
OS: Windows (All)   
Whiteboard:
Crash report or crash signature: Regression By:

Description Rainer Bielefeld Retired 2012-06-22 10:53:17 UTC
Steps how to reproduce with parallel installation of Master "LOdev " 3.7.0.0.alpha0+   - WIN7 Home Premium (64bit) ENGLISH UI [Build ID: 8d39b7]" (tinderbox: W2008R2@16-minimal_build, pull time 2012-06-20 04:38:46):

1. create new WRITER document from LibO start center
2. If necessary menu 'Tools -> Options -> LibO -> General -> 
   Use Libo File dialogs' 
3. Menu 'File -> Save as'
4. Click 'New Folder' Iocn
5. Input New folder Filename "this: is not allowed"  <Save>
   Expected: Error message "Error Saving Document Untitled1: The file name 
             contains invalid characters"
   Actual: Nothing! No folder created, no error message

Same with Server Installation of  "LibreOffice 3.6.0.0.beta2  English UI/Locale [Build-ID: f010139] on German WIN7 Home Premium (64bit) 

Was ok:
with Server installation of Master "LOdev 3.6.0alpha0+  – WIN7 Home Premium (64bit) ENGLISH UI [Build ID: 7175cee]" (tinderbox: Win-x86@6-fast, pull time 2012-05-16 22:07:37)
Comment 1 Julien Nabet 2012-06-30 00:08:29 UTC
Just for information, since this bug is marked as "Windows All" bug.
On pc Debian x86-64, with master sources updated today, I don't reproduce this problem.
(wasn't easy to try to reproduce since I could create a folder containing ":" or others, I succeeded in trying by using this sequence : \/{})
Comment 2 Thomas Hackert 2013-06-24 17:30:05 UTC
Hello Julien, *,
if I follow Rainer's description, I can confirm this bug, but if I use something like "This/ is not allowed" LO Version: 4.1.0.1 Build ID: 1b3956717a60d6ac35b133d7b0a0f5eb55e9155 under Debian Testing AMD64, just reopens the "Create new folder" dialog again and again ... :( Shouldn't there be an error message like "Illegal use of character $bla" or the like?
Comment 3 Julien Nabet 2013-06-26 18:20:02 UTC
Michael: on pc Debian x86-64 with master sources, I don't reproduce what Rainer had but reproduced what thackert got, ie no error message when invalid folder name. Should we close this tracker and open a new one or just change the description of the bug?
Comment 4 QA Administrators 2014-02-02 02:06:44 UTC
Dear Bug Submitter,

Please read the entire message before proceeding.

This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INVALID due to lack of needed information.

For more information about our NEEDINFO policy please read the wiki located here: 
https://wiki.documentfoundation.org/QA/FDO/NEEDINFO

If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed.


Thank you for helping us make LibreOffice even better for everyone!


Warm Regards,
QA Team
Comment 5 QA Administrators 2014-02-26 19:31:14 UTC
Dear Bug Submitter,

Please read this message in its entirety before proceeding.

Your bug report is being closed as INVALID due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided):

a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present

b) Provide easy to reproduce steps – the simpler the better

c) Provide any test case(s) which will help us confirm the problem

d) Provide screenshots of the problem if you think it might help

e) Read all comments and provide any requested information

Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. 
Please do not:
a) respond via email 
b) update the version field in the bug or any of the other details on the top section of FDO