Bug 62277

Summary: Consecutive and duplicated error messages when save to overwrite a document without permission.
Product: LibreOffice Reporter: Yifan Jiang <yfjiang>
Component: filters and storageAssignee: Not Assigned <libreoffice-bugs>
Status: NEW --- QA Contact:
Severity: normal    
Priority: medium    
Version: 3.4.6 release   
Hardware: Other   
OS: All   
Whiteboard:
i915 platform: i915 features:
Attachments: how the boxes looks like in sequence.
how the boxes looks like in sequence.

Description Yifan Jiang 2013-03-13 08:44:26 UTC
Created attachment 76455 [details]
how the boxes looks like in sequence.

Platform: All
Build:    LO 4.0

Steps
-----

    1. $ touch ~/foo.odt; chmod 644 ~/foo.odt; sudo chown root:root ~/foo.odt

    2. Launch writer with an ordinary user

    3. Save the document as ~/foo.odt

    4. Confirm by clicking "Yes" button to overwrite the existed file

Problem
-------

    Of course this is not allowed since the foo.odt is owned by root.

    But there will be 3 consecutive error msg boxes popping out one by
    one after confirming to overwrite the existed odt. (snap shots
    attached)

    I guess it makes sense to alarm only once :)

    
    
Extra Info
----------

    * The only problem happens in SLE HA 11 SP3 chart. When trying similar
      steps in chart SLES11 sp3 and SLED11 sp3, it works all fine.
Comment 1 Yifan Jiang 2013-03-13 08:45:52 UTC
> Extra Info
> ----------
> 
>     * The only problem happens in SLE HA 11 SP3 chart. When trying similar
>       steps in chart SLES11 sp3 and SLED11 sp3, it works all fine.

I am sorry please ignore this garbage info, just it was generated from my local bug report "template" :)
Comment 2 Yifan Jiang 2013-03-13 08:53:36 UTC
Created attachment 76457 [details]
how the boxes looks like in sequence.

a correction of the original one.
Comment 3 Petr Mladek 2013-03-13 11:02:21 UTC
it seems to be pretty old problem. I see it even with 3.4.6 build. I did not tested any earlier one.

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.