Description: when LibreOffice installs, it offers to install a startup enhancement that is being set in the StartUp folder. As in my bug Bug 152542 this sometimes causes in 90 percent to fail to open files that are password protected. So is here the case with a BASE file that has a spreadsheet embedded which had been password protectet. Steps to Reproduce: 1. install LibreOffice but opt-in and tick the option when asked "Load LibreOffice 7.x during system startup" 2. this will drop a shortcut named: quickstart.exe to your Windows startUp folder to boost LibreOffice loading times for large office files 2. create a generic spreadsheet with a table of 3 columns and 3 rows (being the records for the base file later on see step 7.) 3. save the table (spreadsheet) but use a password protection via “Save as…" save with password" 4. the following dialog will ask you to enter your new password twice 5. create a new database, but connect to an existing database (point with the browser to your earlier created spreadsheet) 6. now you may have to enter your password to be able to open that file and it will be put to the “Tables” tab 7. Save the new base-file.odb in the same folder next to your spreadsheet 8. have your computer restarted! to make sure quickstart.exe gets initialized via the shortcut from the Windows startup folder (from within the current user or all default users) 9. this is now the moment for what this bug is about: 10. when Windows has completed its startup routine, a tiny white icon should be shown in the taskbar next to the clock. This indicates that quickstart has been loaded. If quickstart hasn’t been loaded and you open any LibreOffice file you may be shown a splash screen of “LibreOffice” 11. jump to your folder with the new BASE.odb and spreadsheet that you created 12. open the BASE file then click on TABLES which should now ask you for the password that refers to your spreadsheet 13. make sure you enter the correct password 14. In my case the password wasn’t accepted even I had absolutely no mistake 15. By kicking out (ending by right click) the tiny little app quickstart from the task bar, and heading back to step 12 voilà it opens your BASE file 16. this proves that quickstart has an issue 17. If you try to find quickstart.exe from the Windows folder or the LibreOffice folder and have it run on your own then the password procedure above will work surprisingly at no error Actual Results: file error when opening files right after Windows startup has completed caused by the shortcut "quicksart.exe" Expected Results: quickstart.exe from the startup folder should open of office files especially initially afer windows has started. Reproducible: Always User Profile Reset: No Additional Info: If you close the tiny app called quickstart.exe and try to open any files again that had been failed to open, it will work fine then until next Windows boot. It is irrelevant whether the Office file you wish to open is password protected or not.
Created attachment 187166 [details] screenshot for quickstart at time of installing LO
Created attachment 187167 [details] screenshot when creating a new base.odb
the point I would like to emphasis is, that even the entered password for the spreadsheet being entered at the time of the database trying to open the spreadsheet, the connection to the spreadsheet fails, saying the password was incorrect. But, when closing the quickstart.exe then everything works fine with entering the correct password and then BASE can open the spreadsheet as a database. I also have an old Windows 8.1 32-Bit laptop, there is no such behavior, all works as supposed to.
HI, I don't know what kind of additional Info your are requesting here. Perhaps it is relatdt to the Quickstart.exe. Well, I was told it was one published in order to have most of the office package being loaded right at the beginning of Windows starting it self up. I delivered then an enhanced time elapsed from the moment you double click an office document until it gets open to full. Nowadays I see that with the high performance CPU and perhaps 16GB of RAM there seems only a fraction of seconds difference between, starting an office file with or without the quckstart.exe being active or not. But, for Laptops of older generations at 4 GB RAM and below 2 GHz it becomes a valuable factor having quickstart working in the background. Only problem is, nowadays the first file to be opened fails to open. The only workaround is to have the quickstart.exe from the taskmenu be closed, go to startup folder and have it restarted.
Hi, thank you for reporting the bug. Before I try to reproduce it, please could you confirm which version of Windows you are using?
Hi Joseph, sorry for being late. Nowadays I am using 7.5.5.1 and it is still a problem. But this issue has been much disturbing me for a year or so, meaning many versions earlier may be affected. feel free to ask further questions or explanations to my bug report, if it was difficult to comprehend. regards, Harry
[Automated Action] NeedInfo-To-Unconfirmed
Created attachment 188285 [details] screenshot to LO load error
Created attachment 188286 [details] screenshot
Created attachment 188287 [details] screenshot to error 2
Created attachment 188288 [details] screenshot for entering a password BASE connecting to a CAC spreasdheet with a password
today, I received the error again, meaning it sometimes does not show up, only sometimes. Not sure this was related to the fact, that I had my computer on hybernation mode turned of last night. So, what happened: I have a LO BASE file, that connects to a SPREADSHEET which is password protected. With the quickstart.exe app that was active yesterday prior to the hybernation mode, it could not understand my correct password. As a work-around I closed/killed that tiny app called within the task manager, then had my BASE file start again, entered the correct password - it opened fine. Then, I started the tiny app called quickstart.exe from the Startup folder, and it also opened my BASE file and accepted my correct password to the Spreadsheet attached see the screen shots to the errors from the pop-up.
Hello, WORKSFOR ME the bug/behaviour has not occurred again for a long time while using later versions up to LO V24.8 dev.
Likely the same as bug 152542 by the same author. Closing according to comment 13.