1199085 - Profile zapped with last update

Status: RESOLVED INCOMPLETE

(Firefox :: Untriaged, defect)

Description

[Yani]

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:43.0) Gecko/20100101 Firefox/43.0
Build ID: 20150825030212

Steps to reproduce:

What set to use Profile Manager as the default


Actual results:

A new profile was created and profile manage is no longer the default start up.


Expected results:

Profile manage then Firefox.

If this isn't 'just me' then it occurred in the last update.

Comment 1

[Andre Klapper]

Hi reporter, 
unfortunately this report is not very useful because it does not describe the problem well. If you have time and can still reproduce the problem, please read https://developer.mozilla.org/en-US/docs/Mozilla/QA/Bug_writing_guidelines and add a more useful description to this report.

Comment 2

[Yani]

Last update lost the profile and created a new one. If that has happened to others I'll follow up. If not I'll just blame Windows 10 which has become somewhat unstable. 

But I'm sorry my English as so putrid. :)

Comment 3

[Yani]

I notice something else here too.

xpinstall.signatures.required == false

It makes sense that this setting was lost when a new profile was created. I've since set it back to false. 

Now before the last update there were some issues. For example, Adblocker and youTube weren't very happy. 

But the Web developer addon was fine. The Addon doesn't have an incompatibility warning so I assume it have been updated to the signature system.

If in the Addon Manager I click Options all hell breaks loose. Every action after that get a beep and I'm left with no choice but to use the Task Manager to kill Minefield.

Nor does this Addon's menu appear. 

It is possible that they updated the Addon at the same time as the last Minefield update but that seems a tad unlikely.

Comment 4

[Yani]

Well I was going to say the same applies to all Addons. I was only able to post the above by navigating using the keyboard (Tab, Control Tab etc)

But it just corrected itself. Likely as I had to restart and perhaps there was an update waiting? Anyway it isn't the case now.

Comment 5

[Yani]

Last update 28 August 1:23:40 AM

I assume that is my time and it is 9:30 PM here now.

That's odd... there no real sign of a change. The computer has been rebooted, Minefield restarted numerous times and the error persisted until I mention it here. 

Has Firefox developer feelings and become proactive and aware of what is written in this forum? SPOOKY!

;)

Comment 6

[ovidiu boca[:Ovidiu]]

Hi,

To reproduce this issue, please add some clear steps that can help me to test it.

Comment 7

[ovidiu boca[:Ovidiu]]

Based of lack of information from the reporter this bug will have the Status: Resolved as incomplete.
If you want to add more info that can help to understand this bug please reopen it.