Closed
Bug 343602
Opened 18 years ago
Closed 17 years ago
profile-startup-category notifications don't happen if profile is specified
Categories
(SeaMonkey :: Startup & Profiles, defect)
SeaMonkey
Startup & Profiles
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: ajschult784, Assigned: ajschult784)
Details
(Keywords: fixed-seamonkey1.1a)
Attachments
(2 files)
5.58 KB,
patch
|
Biesinger
:
review+
neil
:
superreview+
kairo
:
approval-seamonkey1.1a+
|
Details | Diff | Splinter Review |
2.25 KB,
patch
|
neil
:
review+
neil
:
superreview+
kairo
:
approval-seamonkey1.1a+
|
Details | Diff | Splinter Review |
profile-startup-category notifications happen in nsProfile::LoadDefaultProfileDir, but that method is not called if the commandline included the profile (ProcessArgs would have called SetCurrentProfile). It seems that the notifications should happen at the end of SetCurrentProfile. LoadDefaultProfileDir also does pref conversion to UTF8, which seems like another thing that should live in SetCurrentProfile.
Assignee | ||
Comment 1•18 years ago
|
||
This just moves things from LoadDefaultProfileDir into SetCurrentProfile.
Comment 2•17 years ago
|
||
Comment on attachment 228494 [details] [diff] [review] patch I'm sorry, I don't even kinda-sorta own this code and don't want to.
Attachment #228494 -
Flags: review?(benjamin)
Assignee | ||
Updated•17 years ago
|
Attachment #228494 -
Flags: review?(cbiesinger)
Assignee | ||
Comment 3•17 years ago
|
||
It seems this stuff is not used by toolkit apps
Component: Profile: BackEnd → Profile: Manager
Product: Core → Mozilla Application Suite
Assignee | ||
Comment 4•17 years ago
|
||
The only effect of this bug is that the update notification doesn't work. But that seems like a serious enough problem to need this for 1.1
Flags: blocking-seamonkey1.1a?
Updated•17 years ago
|
Flags: blocking-seamonkey1.1a? → blocking-seamonkey1.1a+
Comment 5•17 years ago
|
||
Comment on attachment 228494 [details] [diff] [review] patch I don't know this code very well but it looks OK to me. Please don't add trailing whitespace on those new lines. (This does make the listener run on live profile switching, but that seems ok)
Attachment #228494 -
Flags: review?(cbiesinger) → review+
Assignee | ||
Updated•17 years ago
|
Attachment #228494 -
Flags: superreview?(neil)
Comment 6•17 years ago
|
||
(In reply to comment #5) >This does make the listener run on live profile switching, but that seems ok) No it doesn't, because the update notifier assumes it only starts once.
![]() |
||
Comment 7•17 years ago
|
||
Hmm, can we get a fix into 1.8 branch within the next week, so we can get 1.1a out in time?
Assignee | ||
Comment 8•17 years ago
|
||
This makes the update notifier not notify twice after switching profiles.
Attachment #234338 -
Flags: superreview?(neil)
Attachment #234338 -
Flags: review?(neil)
Comment 9•17 years ago
|
||
Comment on attachment 234338 [details] [diff] [review] fix update notifier >-const kDebug = false; >+const kDebug = true; Did you really mean this? ;-) >+ // Check if we've already been called. >+ if (initialized) >+ return; >+ initialized = true; You should use this.mInitialized etc, not a global. sr=me with this fixed.
Attachment #234338 -
Flags: superreview?(neil)
Attachment #234338 -
Flags: superreview+
Attachment #234338 -
Flags: review?(neil)
Attachment #234338 -
Flags: review+
Comment 10•17 years ago
|
||
Comment on attachment 228494 [details] [diff] [review] patch >+ nsCOMPtr <nsIProfileStartupListener> listener = do_CreateInstance(contractidString.get(), &rv); Since we'll notify on a profile switch, we need do_GetService here. Otherwise we'll create new update notifiers on each profile switch! sr=me with this fixed.
Attachment #228494 -
Flags: superreview?(neil) → superreview+
![]() |
||
Comment 11•17 years ago
|
||
Comment on attachment 228494 [details] [diff] [review] patch a=me for 1.1 given it works on trunk.
Attachment #228494 -
Flags: approval-seamonkey1.1a+
![]() |
||
Comment 12•17 years ago
|
||
Comment on attachment 234338 [details] [diff] [review] fix update notifier a=me for 1.1 given it works on trunk.
Attachment #234338 -
Flags: approval-seamonkey1.1a+
Assignee | ||
Comment 13•17 years ago
|
||
FIXED on trunk and branch
Assignee | ||
Comment 14•17 years ago
|
||
this exposed the fact that nsUpdateNotifier gets leaked (bug 349323)
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Assignee | ||
Comment 15•17 years ago
|
||
oops, meant to leave this fixed
Status: REOPENED → RESOLVED
Closed: 17 years ago → 17 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•