Closed
Bug 531532
Opened 15 years ago
Closed 15 years ago
Crash for profiles with a non-existent non-relative profile location
Categories
(Toolkit :: Startup and Profile System, defect)
Toolkit
Startup and Profile System
Tracking
()
RESOLVED
FIXED
mozilla1.9.3a1
Tracking | Status | |
---|---|---|
status1.9.2 | --- | beta5-fixed |
People
(Reporter: Gabri, Assigned: Gabri)
Details
Attachments
(1 file)
764 bytes,
patch
|
benjamin
:
review+
beltzner
:
approval1.9.2+
|
Details | Diff | Splinter Review |
Steps to reproduce: - Download and unzip a trunk build on your desktop - Make a batch file with ("profile" folder must not exist): start C:\......\firefox\firefox.exe -profile profile Message returned: "Firefox is already running, but is not responding. To open a new window, you must first close the existing Firefox process, or restart your system.".
Assignee | ||
Comment 1•15 years ago
|
||
It should create the "profile" folder automatically or display to the user if he wants to create it.
Assignee | ||
Comment 2•15 years ago
|
||
It works, I hope benjamin could review it.
Attachment #414916 -
Flags: review?(benjamin)
Updated•15 years ago
|
Attachment #414916 -
Flags: review?(benjamin) → review+
Updated•15 years ago
|
Assignee: nobody → gabri.best
Component: Profile: BackEnd → Startup and Profile System
Keywords: checkin-needed
Product: Core → Toolkit
QA Contact: profile-manager-backend → startup
Comment 3•15 years ago
|
||
Dup of bug 278860?
Comment 4•15 years ago
|
||
No, not at all.
Comment 5•15 years ago
|
||
(In reply to comment #4) > No, not at all. Benjamin Smedberg, what is difference of this bug from problem of bug 278860? Proposed patch to this bug never covers problem of bug 278860? Or you saying that "Firefox is already running, but is not responding. ..." when non-relative path(this bug) is absolutely different problem from the message/phenomenon when relative path(bug 278860)? Or this bug is really for crash even though Crash-ID is not reported to this bug?
Assignee | ||
Comment 6•15 years ago
|
||
This bug is specifically about -profile so it's not a dup of bug 278860. I'll take a look to bug 278860 soon :)
Assignee | ||
Updated•15 years ago
|
Attachment #414916 -
Flags: approval1.9.2?
Comment 7•15 years ago
|
||
Comment on attachment 414916 [details] [diff] [review] proposed patch a192=beltzner
Attachment #414916 -
Flags: approval1.9.2? → approval1.9.2+
Comment 8•15 years ago
|
||
(In reply to comment #6) > I'll take a look to bug 278860 soon :) Gabriele Best, I hope you'll resolve bug 459638 too, which Benjamin closed as WONTFIX once in the past :-) (Note: I understand why Benjyamin closed that bug as WONTFIX once, but I can't accept WONTFIX of that bug, although I can explain "why Bug 491295 was WONTFIXE'ed/it's reasonable/we should acceptt it" to users and bug openers for similar phenomenon to Bug 491295.)
Comment 9•15 years ago
|
||
http://hg.mozilla.org/mozilla-central/rev/0d807039820e
Keywords: checkin-needed
Target Milestone: --- → mozilla1.9.3a1
Updated•15 years ago
|
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → FIXED
Assignee | ||
Updated•15 years ago
|
Keywords: checkin-needed
Comment 10•15 years ago
|
||
http://hg.mozilla.org/releases/mozilla-1.9.2/rev/0b76e7842754
status1.9.2:
--- → final-fixed
Keywords: checkin-needed
Assignee | ||
Updated•15 years ago
|
Target Milestone: mozilla1.9.3a1 → mozilla1.9.2
Comment 11•15 years ago
|
||
target should stay to the first branch where the patch has been pushed.
Target Milestone: mozilla1.9.2 → mozilla1.9.3a1
You need to log in
before you can comment on or make changes to this bug.
Description
•