Bug 68230 - Other: LO 4.2 allowing two preference panes
Summary: Other: LO 4.2 allowing two preference panes
Status: RESOLVED DUPLICATE of bug 31915
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: LibreOffice (show other bugs)
Version:
(earliest affected)
4.2.0.0.alpha0+ Master
Hardware: Other macOS (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard: BSA
Keywords:
Depends on:
Blocks:
 
Reported: 2013-08-17 17:55 UTC by retired
Modified: 2013-08-28 00:15 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:


Attachments
screenshot of the two pref panes (303.40 KB, image/png)
2013-08-17 17:55 UTC, retired
Details

Note You need to log in before you can comment on or make changes to this bug.
Description retired 2013-08-17 17:55:40 UTC
Created attachment 84182 [details]
screenshot of the two pref panes

Problem description: two pref panes are open. should not be allowed.

Version: 4.2.0.0.alpha0+
Build ID: 7e7a83b73dad2a9a2c73826f61a81c4c774d2c9d
TinderBox: MacOSX-X86_64@43, Branch:master, Time: 2013-08-16_22:48:57

Steps to reproduce:
1. Open LO 4.2 master build on OS X
2. hit cmd + , to show the preferences
3. the pref pane opens as expected
4. now select via menu LibreOfficeDev > Preferences...
5. a second pref pane opens up
-> Ooops.

Current behavior: 2 panes

Expected behavior: 1 pane

              
Operating System: Mac OS X
Version: 4.2.0.0.alpha0+ Master
Comment 1 Emir Sarı 2013-08-17 18:43:48 UTC
Confirmed under Version: 4.2.0.0.alpha0+
Build ID: f10f5ca011c3d06d3470b9e21bda13d505cfe93e
TinderBox: MacOSX-X86_64@43, Branch:master, Time: 2013-08-16_00:09:5
Comment 2 How can I remove my account? 2013-08-26 07:34:58 UTC
I assume his can be marked as a duplicate of the oldest still open Mac-specific LibreOffice bug, bug#31915. Will try to make the title of that bug more generic.

*** This bug has been marked as a duplicate of bug 31915 ***
Comment 3 retired 2013-08-28 00:15:24 UTC
Thanks for the heads-up Tor. This is one old bug then. But fixing seems to be not trivial from what I read in the original bug. Hope this can be dealt with somehow...