I much work in Libreoffice. Allmost all is ok. But time to time my videocard hangs. Screen become black or freeses. All programs continue to work, but I can see nothing. An I should save all unsaved documents. I can switch to text console or press some hotkeys. I propose: create small program that forces all instances of Libre and Open office to save documents and exit. If document created and never saved then it not need to been saved, only close. I can then start this program form text mode console or from ssh or assign it on keybinding in desktop.
[This is an automated message.] This bug was filed before the changes to Bugzilla on 2011-10-16. Thus it started right out as NEW without ever being explicitly confirmed. The bug is changed to state NEEDINFO for this reason. To move this bug from NEEDINFO back to NEW please check if the bug still persists with the 3.5.0 beta1 or beta2 prereleases. Details on how to test the 3.5.0 beta1 can be found at: http://wiki.documentfoundation.org/QA/BugHunting_Session_3.5.0.-1 more detail on this bulk operation: http://nabble.documentfoundation.org/RFC-Operation-Spamzilla-tp3607474p3607474.html
I'm setting this as a High Enhancement as I think it would be useful for many of us :) Thanks for the suggestion
Is this something that should be programmed in LibO or as an external program? Do video card problems still occur to this extent? Maybe a WONTFIX.
Set "AutoSave/AutoRecovery" meta bug as blocking bug due to the fact that autorecovery should work correctly to bring all the stuff you didn't save back up the next time you run LO. That would be the best way to fix this issue for all instances. That would mean a WORKSFORME.
Changing priority back to 'medium' since the number of duplicates is lower than 5
I have found that "pkill -6 soffice" triggers an emergency save, so that should help for immediate results. (6 == SIGABRT) Also, as comment 4 notes, autorecovery should save any modified documents (after 10 minutes). [Note that this was broken - off by default - in 7.x, but fixed for 24.2.]. I agree with WORKSFORME - certainly there is no call for a LO specific command line tool to be introduced for this purpose.