Bug 88269 - FILESAVE / EDITING:becomes non-responsive if a database opened for editing is saved as a new file name whilst a report is open for editing.
Summary: FILESAVE / EDITING:becomes non-responsive if a database opened for editing is...
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Database (show other bugs)
Version: 4.3.5.2 release
Hardware: x86-64 (AMD64) All
: medium major
Assignee: Not Assigned
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-01-10 14:34 UTC by James B. Byrne
Modified: 2015-01-11 16:34 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:


Attachments

Description James B. Byrne 2015-01-10 14:34:45 UTC
LO opens the spinning colour wheel of death and becomes non-responsive if a database opened for editing is saved as a new file name whilst a report is open for editing.  When the focus is returned to the report builder window a notice that the connection to the database has been lost. The user is then given the choice of attempting to reconnect or not.  Attempting to reconnect causes LO Base to enter a non-responsive state.  

The open windows in LO may be moved and the gui refreshes when this is done but none of the controls, toolbars or menu items respond to mouse selection. Nor to the corner controls of the OSX interface respond.  The only solution is to force quit the application from the OS. 

The LO Base did not change to the newly saved odb document and when LO was reopened after the forced quit it was the original odb document that needed recovery.  This is unexpected as the other components of LO switch editing focus to the new document name when save as is used.
Comment 1 raal 2015-01-11 16:34:17 UTC
I can confirm with Version: 4.5.0.0.alpha0+
Build ID: a272f5b7b30f356418ecf28eb95d066f081d1624
TinderBox: Linux-rpm_deb-x86_64@46-TDF, Branch:master, Time: 2015-01-09_09:50:59


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.