Issue 69149 - "personal settings are locked" message is inadequate
Summary: "personal settings are locked" message is inadequate
Status: CLOSED IRREPRODUCIBLE
Alias: None
Product: General
Classification: Code
Component: ui (show other issues)
Version: OOo 1.0.3
Hardware: All All
: P3 Trivial (vote)
Target Milestone: ---
Assignee: AOO issues mailing list
QA Contact:
URL:
Keywords: needmoreinfo
Depends on:
Blocks:
 
Reported: 2006-08-31 17:18 UTC by bkorb
Modified: 2017-05-20 10:02 UTC (History)
2 users (show)

See Also:
Issue Type: ENHANCEMENT
Latest Confirmation in: ---
Developer Difficulty: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this issue.
Description bkorb 2006-08-31 17:18:32 UTC 
The "personal settings are locked" message is frustratingly stupid.
Googling for help yields next to nothing and the message gives you
absolutely no clue what to do.  You have several archived emails
about this, so it is hard to imagine you haven't noticed the issue.
Please include information about ~/.openoffice*/.lock in your message.
Thanks.  It might also be nice if your default installation (which
apparently does not include the help subsystem) were to point to
the self help pages so I do not have to filter through all the
"pay us to answer your question" pages before finding those self-help
pages, too.
Comment 1 thorsten.martens 2006-09-01 07:00:00 UTC 
TM->requirements: please have a look, thanks !
Comment 2 scriblerus 2011-02-04 17:07:42 UTC 
After installation, I tried to run OO but got the message that either another
instance of OO was running or my personal settings were locked.  The advice
provided in the message was unintelligible to me, and I gave up: uninstalled OO.
Comment 3 Edwin Sharp 2014-02-21 11:29:37 UTC 
How did you receive this message?
Comment 4 bkorb 2014-02-22 18:24:50 UTC 
(In reply to Edwin Sharp from comment #3)
> How did you receive this message?

Let me ask, how well do _you_ remember how you got an error message 8 years ago?
Even if I could remember, what is the likelihood that the code that emitted it (probably written a decade ago) is still current?  So I recommend:

1. close this issue as too old to believe

2. remember for the future that error messages are important and need to be helpful.
Comment 5 Edwin Sharp 2014-02-23 08:46:20 UTC 
Every bug gets a chance, no matter how old.
Thank you.