Bug 152773 - Cannot save modified document any more - LO becomes unresponsive
Summary: Cannot save modified document any more - LO becomes unresponsive
Status: RESOLVED WORKSFORME
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
7.4.3.2 release
Hardware: All Windows (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-12-31 12:51 UTC by Helmut Leininger
Modified: 2023-01-02 14:09 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:

Attachments
Pinzgau.odt (367.34 KB, application/vnd.oasis.opendocument.text)
2022-12-31 12:57 UTC, Helmut Leininger 		Details
Pinzgau-1.odt (29.47 KB, application/vnd.oasis.opendocument.text)
2022-12-31 12:59 UTC, Helmut Leininger 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Helmut Leininger 2022-12-31 12:51:44 UTC 

    


    


      



        
          Comment 1
        

        
          Helmut Leininger

        

        
        

        
          2022-12-31 12:57:50 UTC
        

      






Created attachment 184410 [details]
Pinzgau.odt

existing document which cannot be saves after modification

    


    


      



        
          Comment 2
        

        
          Helmut Leininger

        

        
        

        
          2022-12-31 12:59:12 UTC
        

      






Created attachment 184411 [details]
Pinzgau-1.odt

Document with content to be appended (copy & paste) to Pinzgau.odt

    


    


      



        
          Comment 3
        

        
          Helmut Leininger

        

        
        

        
          2022-12-31 13:02:21 UTC
        

      






If I append some data to Pinzgau.odt (e.g. copy & paste the content of Pinzgu-1.odt) I cannot save it any more. LO becomes unresponsive at ctrl-S or when saving from the menu.

    


    


      



        
          Comment 4
        

        
          Stéphane Guillou (stragu)

        

        
        

        
          2022-12-31 15:11:18 UTC
        

      






I was able to save Pingzau.odt after appending everything from Pingzau-1.odt, using:

Version: 7.4.3.2 / LibreOffice Community
Build ID: 1048a8393ae2eeec98dff31b5c133c5f1d08b890
CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3
Locale: en-AU (en_AU.UTF-8); UI: en-US
Calc: threaded

- Can you please paste the info from "Help > About LibreOffice" here?
- Can you please try again in safe mode to see if the issue persists? (Help > Restart in safe mode)

    


    


      



        
          Comment 5
        

        
          Helmut Leininger

        

        
        

        
          2022-12-31 15:30:48 UTC
        

      






The problem persists also in safe mode.

Version info:
Version: 7.4.3.2 (x64) / LibreOffice Community
Build ID: 1048a8393ae2eeec98dff31b5c133c5f1d08b890
CPU threads: 16; OS: Windows 10.0 Build 22621; UI render: Skia/Raster; VCL: win
Locale: de-AT (de_AT); UI: de-DE
Calc: CL

    


    


      



        
          Comment 6
        

        
          Helmut Leininger

        

        
        

        
          2022-12-31 15:48:24 UTC
        

      






I retried after deleting the user directory (C:\Users\hlein\AppData\Roaming\LibreOffice\4) - works ok.
So, there must have been some bad heritage from severalupdates to LibreOffice.

    


    


      

          
            
          


        
          Comment 7
        

        
          QA Administrators

        

        
        

        
          2023-01-01 03:24:22 UTC
        

          
            Comment hidden (obsolete)
          
      






    


    


      



        
          Comment 8
        

        
          Stéphane Guillou (stragu)

        

        
        

        
          2023-01-02 14:09:53 UTC
        

      






Thank you for testing and reporting back, Helmut. Closing as "works for me" as a profile reset resolved the issue (could have been somehow corrupted) but please comment here if you witness the issue again!