1 |
Hello, Mick. |
2 |
|
3 |
On Sat, Aug 01, 2015 at 04:19:32PM +0100, Mick wrote: |
4 |
> On Thursday 30 Jul 2015 19:59:25 you wrote: |
5 |
> > On Thursday 30 Jul 2015 19:23:03 Alan Mackenzie wrote: |
6 |
> > > Hello, Gentoo. |
7 |
|
8 |
> > > Over the course of the last 24 hours, Firefox 38.1.0 became stable in |
9 |
> > > portage, so I merged it in. |
10 |
|
11 |
> > > What a mistake! |
12 |
|
13 |
> > > All my existing configuration (including for NoScript+), all my |
14 |
> > > bookmarks, all record of previous visits to site - gone, deleted, |
15 |
> > > vanished. I'm not happy about that. |
16 |
|
17 |
> > > The usability of the program has gone down, down, down. Not a lot seems |
18 |
> > > to work properly, anymore. For example, it used to be that you could |
19 |
> > > mark a selection of "your" cookies then delete them in one operation. |
20 |
> > > Now you have to mark a single cookie and delete it, mark the next cookie |
21 |
> > > and delete it, .... Even the screen area where the current URL is |
22 |
> > > displayed is now displayed in low-contrast miniscule type, so that I can |
23 |
> > > barely read it. |
24 |
|
25 |
> > > What on earth are the upstream developers thinking about? Destroying |
26 |
> > > somebody's configuration is not a nice thing to do. |
27 |
|
28 |
> > > I've a feeling that all this must have been discussed here quite |
29 |
> > > recently, so apologies if I'm dredging up old stuff. Still, a |
30 |
> > > recommendation as to how I might proceed would be welcome. Should I go |
31 |
> > > back to 31.8.0 and stay there, or would I be better going with some fork |
32 |
> > > of firefox? |
33 |
|
34 |
> > > Has my old config/cookies/... actually been physically destroyed, or is |
35 |
> > > it just being disregarded by 38.1.0? Looking at my ~/.mozilla/firefox |
36 |
> > > doesn't give me much hope. |
37 |
|
38 |
> > > Yours, in anger. |
39 |
|
40 |
> [snip ...] |
41 |
> > Someone else has already posted about losing their FF profile and settings. |
42 |
> > This however has not happened here. |
43 |
|
44 |
> > Sorry I can't shed more light on this problem. |
45 |
|
46 |
> Until it happened here too ... :-( |
47 |
|
48 |
> So, I find myself with one box having the problem of ALWAYS wanting to start |
49 |
> up with some 'dev-edition-default' profile, which has a dark bacground theme |
50 |
> and is void of previous user settings. The old profile with the user's |
51 |
> bookmarks, extensions, etc. is called 'default'. Firefox starts with the |
52 |
> Profile Manager pop-up giving me a choice which profile to use, but selecting |
53 |
> the 'default' profile and asking it not to ask again at start up does not work |
54 |
> as expected. |
55 |
|
56 |
No, indeed it doesn't. |
57 |
|
58 |
> The 'default' profile selection does not stick. Deleting the new |
59 |
> 'dev-edition-default' profile causes it to be recreated afresh at the |
60 |
> next start up. |
61 |
|
62 |
Yes. This is the sort of developer attitude that is making me want to |
63 |
use a proper browser. What the heck does a browser need "prefiles" for, |
64 |
anyway? It's supposed to be a web browser, for goodness sake. |
65 |
|
66 |
> Anyway, the box without this problem does not have USE="bindist" set, while |
67 |
> the PC with the above problem does. I just removed bindist from make.conf |
68 |
> (not sure why it was there) and I rebuilt Firefox. The stuck dev-edition- |
69 |
> fault profile problem is gone! :-) |
70 |
|
71 |
But the bindist USE flag is about branding, and restrictions on the use |
72 |
of trademarks, and stuff like that. And if you look at the ebuild, you |
73 |
will see that this is indeed the only way that bindist is used. So all |
74 |
the messing around that firefox does with these silly profiles is done by |
75 |
some sort of "clever" programming. |
76 |
|
77 |
> HTH. |
78 |
|
79 |
> -- |
80 |
> Regards, |
81 |
> Mick |
82 |
|
83 |
-- |
84 |
Alan Mackenzie (Nuremberg, Germany). |