gnome max-out during sign-in in Firefox.

[home user]

(f29; gnome; Firefox 68.0; all patched late this morning)

While trying to sign on to a financial institution's web site, when I 
start to enter the password, the cpu suddenly gets extremely busy and 
stays that way.  I had to hit the power button.  Upon booting up again, 
I launched ksysguard, and then re-tried the login.  Again I saw the cpu 
essentially max out.  I had to hit the power button.  Upon booting up, I 
launched "top" in a terminal, and then retried the login.  Again the cpu 
essentially maxed out.  "top" showed that gnome was the cpu hog.

I again hit the power button and booted up.  This time I logged in to a 
plasma session.  I was able to log in and do what I had to do with no 
problems.

This one is really strange.  How do I determine what the problem is? 
This problem did not occur before today's "dnf upgrade".  The last 
patching before today was last Thursday.

thanks,
Bill.

[Fred Smith]

On Thu, Jul 25, 2019 at 08:24:07PM -0600, home user via users wrote:
>  (f29; gnome; Firefox 68.0; all patched late this morning)
>  
>  While trying to sign on to a financial institution's web site, when
>  I start to enter the password, the cpu suddenly gets extremely busy
>  and stays that way.  I had to hit the power button.  Upon booting up
>  again, I launched ksysguard, and then re-tried the login.  Again I
>  saw the cpu essentially max out.  I had to hit the power button.
>  Upon booting up, I launched "top" in a terminal, and then retried
>  the login.  Again the cpu essentially maxed out.  "top" showed that
>  gnome was the cpu hog.
>  
>  I again hit the power button and booted up.  This time I logged in
>  to a plasma session.  I was able to log in and do what I had to do
>  with no problems.
>  
>  This one is really strange.  How do I determine what the problem is?
>  This problem did not occur before today's "dnf upgrade".  The last
>  patching before today was last Thursday.
>  
>  thanks,
>  Bill. 
well, firstly, it's bad practice to do a dirty shutdown of a running system.

If you've got top running, you can kill processes from within the
top UI. in top, hit "h" for help. note that "k" will kill processes.

Perhaps you can see which gnome component it is that's hogging RAM
then report that to the appropriate authorities.

Also, sometimes when some process hogs all the memory, it is transient
and if you can be patient it may calm down so you don't have to take
drastic action.

further, it is possible to enable additional columns in top to help
figure out where the memory is going.

One can also try CTRL-ALT-F2 or CTRL-ALT-F3 or similar to get a non-GUI
terminal. those don't use nearly as much system resources as a terminal
window. from there top and other commands may respond better even in
the presence of a runaway process.

Good luck!

>  _______________________________________________
>  users mailing list -- users(a)lists.fedoraproject.org
>  To unsubscribe send an email to users-leave(a)lists.fedoraproject.org
>  Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
>  List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
>  List Archives:
> https://lists.fedoraproject.org/archives/list/[e-mail] 
-- 
---- Fred Smith -- fredex(a)fcshome.stoneham.ma.us -----------------------------
                      The eyes of the Lord are everywhere, 
                    keeping watch on the wicked and the good.
----------------------------- Proverbs 15:3 (niv) -----------------------------

[Tim]

On Thu, 2019-07-25 at 20:24 -0600, home user via users wrote:
>  How do I determine what the problem is? 
>  This problem did not occur before today's "dnf upgrade".  The last 
>  patching before today was last Thursday. 
You can try "dnf history" to see what had changed recently, and see if
anything jumps out at you at being browser- or screen-related.

It could be the website, they may have changed something at the same
time.

-- 
[tim@localhost ~]$ uname -rsvp
Linux 5.0.16-100.fc28.x86_64 #1 SMP Tue May 14 18:22:28 UTC 2019 x86_64

Boilerplate:  All mail to my mailbox is automatically deleted.
There is no point trying to privately email me, I only get to see
the messages posted to the mailing list.

Lucky for you I typed this, you'd never be able to read my handwriting.

[Ed Greshko]

On 7/26/19 1:01 PM, Tim via users wrote:
>  On Thu, 2019-07-25 at 20:24 -0600, home user via users wrote:
> > How do I determine what the problem is? 
> > This problem did not occur before today's "dnf upgrade".  The last 
> > patching before today was last Thursday.
>  You can try "dnf history" to see what had changed recently, and see if
>  anything jumps out at you at being browser- or screen-related.
>
>  It could be the website, they may have changed something at the same
>  time.
>  
And, of course, there is always...

Try a different browser.

Start firefox from the command line with --safe-mode to disable extensions and themes

-- 
Right: I dislike the default color scheme Wrong: What idiot picked the default color
scheme

[Ed Greshko]

On 7/26/19 10:24 AM, home user via users wrote:
>  While trying to sign on to a financial institution's web site
Oh I also wonder about the authentication process page.  Is there a space on the page for
both username and password?  If so, does the problem exist if you pick a random (invalid)
username and then start typing the password?

If the answer to that question is "yes", then is there any harm in disclosing
the
institution to see if someone can duplicate the issue?

-- 
Right: I dislike the default color scheme Wrong: What idiot picked the default color
scheme

[home user]

(replying to all responders)

Actually, the first thing that catches my attention is that when I go to 
the password entry box, the system fans really surge.  This suggests to 
me the CPUs are working at or near capacity.

I also see top and ksysguard repeatedly freezing for several seconds.

(Fred: dirty shutdown; top)
The system was not responding to any keystrokes or trackball clicks. 
The only remaining options are hard reset and hard power off.

(Fred: memory)
The problem is not memory use.  It is CPU load.

(Fred: waiting)
I waited quite a few seconds; certainly long enough to know there's a 
real problem.  It does take a while to move the cursor all over the 
place, clicking in various places (e.g. menus, 'x' in the upper right 
corner of various windows) along the way.

(Fred: CTRL-ALT-F2 or CTRL-ALT-F3)
Does going into this mode kill the session I was in before?  If no, how 
do I get back?  If yes, how do I get back to normal operation without 
rebooting?

(Tim: dnf history)
I put the relevant part of the dnf log here:
"https://paste.fedoraproject.org/paste/IUlWCabjTPra7laQna9xHg".
Firefox was upgraded.  I did not see "gnome" anywhere in the log.  If 
something underneath was patched/upgraded, I would not recognize it.

"dnf history gnome | more" gives this (first 9 lines)
-----
-bash.5[~]: dnf history gnome | more
No transaction which manipulates package 'gnome' was found.
ID     | Command line             | Date and time    | Action(s)      | 
Altered
-------------------------------------------------------------------------------
    833 | -y install --disablerepo | 2019-07-25 11:28 | Install        | 
    1
    832 | upgrade                  | 2019-07-25 11:21 | E, I, U        | 
   76
    831 | upgrade                  | 2019-07-18 11:35 | Upgrade        | 
   55
    830 | upgrade dnf              | 2019-07-18 11:34 | Upgrade        | 
    5
    829 | -y install --disablerepo | 2019-07-11 11:18 | Install        | 
    1
    828 | upgrade                  | 2019-07-11 11:11 | E, I, U        | 
   79 EE
    827 | -y install --disablerepo | 2019-07-04 10:51 | Install        | 
    1
    826 | upgrade                  | 2019-07-04 10:45 | E, I, U        | 
   60
    825 | install Downloads/zoom_x | 2019-07-01 13:16 | Install        | 
    1 EE
-----
I don't think it was a change in the website.  I have the same problem 
with other sites.

(Ed: Start firefox from the command line with --safe-mode ...)
The problem occurs in safe-mode.

(Ed: input fields; web sites)
Both input fields are on the same web page as soon as the page is 
loaded.  The problem occurs with what I assume is a fictitious username 
as well as my real login name.
I've by now experienced these problems with several web sites. Here are 
5 well-known different web sites:
- amazon (https://www.amazon.com/)
- ebay (https://www.ebay.com/)
- Mozilla bugzilla (https://bugzilla.mozilla.org/home)
- Redhat Bugzilla (https://bugzilla.redhat.com/)
- USAJobs (https://www.usajobs.gov/)
and others.

Thank-you everyone for your efforts.
Bill.

[Samuel Sieb]

On 7/26/19 1:16 PM, home user via users wrote:
>  (Fred: CTRL-ALT-F2 or CTRL-ALT-F3)
>  Does going into this mode kill the session I was in before?  If no, how 
>  do I get back?  If yes, how do I get back to normal operation without 
>  rebooting? 
It doesn't kill your session.  You are switching to a different virtual 
console.  I don't know how wayland uses the consoles, but for X, console 
1 is gdm, console 2 is your session, so use ctrl-alt-f3 to open console 
3.  Use alt-f2 or alt-f1 to find your previous session.

[Fred Smith]

On Fri, Jul 26, 2019 at 02:16:15PM -0600, home user via users wrote:
>  (replying to all responders)
>  
>  Actually, the first thing that catches my attention is that when I
>  go to the password entry box, the system fans really surge.  This
>  suggests to me the CPUs are working at or near capacity.
>  
>  I also see top and ksysguard repeatedly freezing for several seconds.
>  
>  (Fred: dirty shutdown; top)
>  The system was not responding to any keystrokes or trackball clicks.
>  The only remaining options are hard reset and hard power off. 
there are often additional choices besides a hard shutdown.
google for "magic sysreq key". 

>  
>  (Fred: memory)
>  The problem is not memory use.  It is CPU load. 
OK. I was thinking of a "swap storm". if the system gets pushed into
heavy swapping (because of too much memory neededfor what is running)
it can slow to a crawl, sometimes taking many minutes to recover once
the memory pressure is relieved.

>  
>  (Fred: waiting)
>  I waited quite a few seconds; certainly long enough to know there's
>  a real problem.  It does take a while to move the cursor all over
>  the place, clicking in various places (e.g. menus, 'x' in the upper
>  right corner of various windows) along the way.
>  
>  (Fred: CTRL-ALT-F2 or CTRL-ALT-F3)
>  Does going into this mode kill the session I was in before?  If no,
>  how do I get back?  If yes, how do I get back to normal operation
>  without rebooting? 
No, the GUI is still there, it's just on another virtual screen.
Usually you can go back there by doing ALT-F1 or CTRL-ALT-F1.


-- 
---- Fred Smith -- fredex(a)fcshome.stoneham.ma.us -----------------------------
                    The Lord detests the way of the wicked 
                  but he loves those who pursue righteousness.
----------------------------- Proverbs 15:9 (niv) -----------------------------

[Ed Greshko]

On 7/27/19 4:16 AM, home user via users wrote:
>  -bash.5[~]: dnf history gnome | more
>  No transaction which manipulates package 'gnome' was found.
>  ID     | Command line             | Date and time    | Action(s)      | Altered
>  -------------------------------------------------------------------------------
>     833 | -y install --disablerepo | 2019-07-25 11:28 | Install        |    1
>     832 | upgrade                  | 2019-07-25 11:21 | E, I, U        |   76
>     831 | upgrade                  | 2019-07-18 11:35 | Upgrade        |   55
>     830 | upgrade dnf              | 2019-07-18 11:34 | Upgrade        |    5
>     829 | -y install --disablerepo | 2019-07-11 11:18 | Install        |    1
>     828 | upgrade                  | 2019-07-11 11:11 | E, I, U        |   79 EE
>     827 | -y install --disablerepo | 2019-07-04 10:51 | Install        |    1
>     826 | upgrade                  | 2019-07-04 10:45 | E, I, U        |   60
>     825 | install Downloads/zoom_x | 2019-07-01 13:16 | Install        |    1 EE 
Well, that simply tells one that 76 packages were affected on 7/25.  If the issue did
surface after that date you'd want to see which packages were altered.

So, you want to do "dnf history info 832"

>  -----
>  I don't think it was a change in the website.  I have the same problem with other
> sites.
>
>  (Ed: Start firefox from the command line with --safe-mode ...)
>  The problem occurs in safe-mode.
>
>  (Ed: input fields; web sites)
>  Both input fields are on the same web page as soon as the page is loaded.  The problem
>  occurs with what I assume is a fictitious username as well as my real login name.
>  I've by now experienced these problems with several web sites. Here are 5 well-known
>  different web sites:
>  - amazon (https://www.amazon.com/)
>  - ebay (https://www.ebay.com/)
>  - Mozilla bugzilla (https://bugzilla.mozilla.org/home)
>  - Redhat Bugzilla (https://bugzilla.redhat.com/)
>  - USAJobs (https://www.usajobs.gov/)
>  and others. 
Have you tried another browser?

Also, if you run "GNOME on Xorg" do you also have a problem (That is Xorg v.s.
the default
Wayland)

-- 
Right: I dislike the default color scheme Wrong: What idiot picked the default color
scheme

[home user]

Good morning,

(responding to Samuel and Fred)
Ctrl-Alt-F2 and Ctrl-Alt-F3 both work.  From there I am able to kill 
Firefox.  That seems brings the system load back to typical.
Alt-F1 returns me to the Gnome graphical session.  The others do not.

(responding to Ed)
>  If the issue did surface after that date.... 
No problem
Wednesdays evening; "dnf upgrade" was done Thursday late 
morning; problems observed Thursday evening.
>  So, you want to do "dnf history info 832" 
For the
results, see here:
"https://paste.fedoraproject.org/paste/oRTWU3TPnKPuw-a98yZkFw".
>  Have you tried another browser? 
Yes.  It takes a few new
identities, but there is no problem if I use 
the Tor browser.  I have not tried any other browsers.  I don't think I 
have any other browsers, and I am adverse to installing any commercial 
browsers.  There is no problem when I use Plasma rather than Gnome.
>  Also, if you run "GNOME on Xorg" do you also have a
> problem
>  (That is Xorg v.s. the default Wayland) 
Yes.

(not responding to anyone specifically)
At this point,
* I can end the CPU near-overload; and
* there are work-arounds.
Those are important, but only a part of the reason for starting this 
thread.  The real problem is still there, and I don't feel it's pinned 
down enough to submit well-written bug(s).  My sense so far is that a 
bug was introduced in the new Firefox, but I can't rule out Gnome.  Are 
there other good candidates for the source of the problem?
* Should a bug be submitted against Firefox?
* Should a bug be submitted against Gnome?
* Is there anything else I should submit a bug against?
Are there any other quick, simple tests I should do before submitting bugs?

thanks,
Bill.

[Tim]

Hi Bill,

On Fri, 2019-07-26 at 14:16 -0600, home user via users wrote:
>  (Tim: dnf history)
>  I put the relevant part of the dnf log here:
>  "https://paste.fedoraproject.org/paste/IUlWCabjTPra7laQna9xHg".
>  Firefox was upgraded.  I did not see "gnome" anywhere in the log. 
>  If something underneath was patched/upgraded, I would not recognize
>  it.
>  
>  "dnf history gnome | more" gives this (first 9 lines)
>  -----
>  -bash.5[~]: dnf history gnome | more
>  No transaction which manipulates package 'gnome' was found.
>  ID     | Command line             | Date and time    | Action(s)      | Altered
>  -------------------------------------------------------------------------------
>      833 | -y install --disablerepo | 2019-07-25 11:28 | Install        |     1
>      832 | upgrade                  | 2019-07-25 11:21 | E, I, U        |    76
>      831 | upgrade                  | 2019-07-18 11:35 | Upgrade        |    55
>      830 | upgrade dnf              | 2019-07-18 11:34 | Upgrade        |     5
>      829 | -y install --disablerepo | 2019-07-11 11:18 | Install        |     1
>      828 | upgrade                  | 2019-07-11 11:11 | E, I, U        |    79 EE
>      827 | -y install --disablerepo | 2019-07-04 10:51 | Install        |     1
>      826 | upgrade                  | 2019-07-04 10:45 | E, I, U        |    60
>      825 | install Downloads/zoom_x | 2019-07-01 13:16 | Install        |     1 EE
>  ----- 
I would look at the history output without grepping for gnome.  There
may be an issue from something without gnome in the name, and we can't
see what the disabled repo was.  I assume that the 
https://paste.fedoraproject.org/paste/IUlWCabjTPra7laQna9xHg log is
unfiltered.

Things that jump out of me from that list are big changes: kernel,
kernel-headers, firefox, and kmod-nvidia.  I presume that you did a
reboot, soon after.

It may be worth looking a bit further back, in case a prior
install/upgrade caused the problem, but you hadn't done anything that
would make you notice it, yet.

NB:  When you update Firefox, you really need to *fully* quit the
program and restart.  I've found that it goes haywire, otherwise.  If
you close a Firefox window, and other Firefox windows are left still
running, it's still running the prior installation.

>  I don't think it was a change in the website.  I have the same
>  problem with other sites.
>  
>  (Ed: Start firefox from the command line with --safe-mode ...)
>  The problem occurs in safe-mode. 
Using safe mode should eliminate any plug-ins as being a cause.  That
still leaves things like scripting, or a change in encryption methods. 
So do all other websites cause problems, or just some?

You mentioned it seems okay in a plasma session.  So I wonder what
isn't run from gnome, under those circumstances?  gnome-settings-
daemon, gnome-keyring?  In Gnome you can see what's in the startup
applications, there must be a similar tool for plasma.

-- 
[tim@localhost ~]$ uname -rsvp
Linux 5.0.16-100.fc28.x86_64 #1 SMP Tue May 14 18:22:28 UTC 2019 x86_64

Boilerplate:  All mail to my mailbox is automatically deleted.
There is no point trying to privately email me, I only get to see
the messages posted to the mailing list.

Next time your service provider asks you to reboot your equipment, ask
them to reboot theirs, first.

[Ed Greshko]

On 7/28/19 7:34 AM, Tim via users wrote:
>  There
>  may be an issue from something without gnome in the name, and we can't
>  see what the disabled repo was. 
Oh, I can answer that.

The new version of akmod-nvida installs the kmod after a kernel install in a different
way
than in the past.  The disable repo is the result of this call by the process.

Command Line   : -y install --disablerepo=*
/tmp/akmods.yilceqq0/results/kmod-nvidia-5.1.19-300.fc30.x86_64-430.26-1.fc30.x86_64.rpm


-- 
Right: I dislike the default color scheme Wrong: What idiot picked the default color
scheme

[home user]

>  I assume that the
>  https://paste.fedoraproject.org/paste/IUlWCabjTPra7laQna9xHg
>  log is unfiltered. 
correct.

>  I presume that you did a reboot, soon after. 
When I do my weekly "dnf upgrade", I am logged in as root, and the only 
things that I explicitly have running are xeyes, ksysguard, and a 
terminal.  My sequence is:
1. "dnf upgrade dnf";
2. "dnf upgrade";
3. sometimes, after the "dnf upgrade" is done and I've received the 
command prompt in the terminal, there seems to be some heavy activity. 
I hear the fans surge and see in ksysguard the CPU load near max for up 
to a few minutes.  So I've learned to wait until ksysguard shows the 
system in an almost idle state (CPU activity almost zero for many 
seconds).  Then...
4. reboot.  I always reboot after "dnf upgrade" and the system is 
settled down.

>  NB:  When you update Firefox, you really need
>  to *fully* quit the program and restart. 
This is taken care of by step 4 above.

>  So do all other websites cause problems, or just some? 
Every login I've tried in Firefox since this last patching has had the 
problem.  No logins in Firefox had problems before this last patching. 
Also, I'm having no problems logging into my e-mail accounts via 
Thunderbird.

>  So I wonder what isn't run from gnome, under those circumstances?
I have no idea.  Someone else?

Has anyone else observed the problem I've having?

By the way, what is all that activity just after "dnf upgrade" completes?

>  Next time your service provider asks you to reboot your equipment,
>  ask them to reboot theirs, first. 
Do you really want the service provider to reboot their equipment?!
:)

thanks,
Bill.

[Ed Greshko]

On 7/28/19 12:00 PM, home user via users wrote:
> By the way, what is all that activity just after "dnf upgrade" completes? 
You have the nvidia drivers installed from, probably, rpmfusion.  So, every time an
upgrade installs a new kernel there will be activity after the upgrade as the akmod
process builds and installs the matching kernel module.

This show in the "dnf history" as...

833 | -y install --disablerepo | 2019-07-25 11:28 | Install        |    1

-- 
Right: I dislike the default color scheme Wrong: What idiot picked the default color
scheme

[home user]

>  You have the nvidia drivers installed from, probably, rpmfusion. ...
I understand.  Thank-you, Ed.

Bill.

[Tim]

Tim (from my tag line):
> > Next time your service provider asks you to reboot your
> equipment,
> > ask them to reboot theirs, first. 
Bill:
>  Do you really want the service provider to reboot their equipment?!
>  :) 
After dealing with some alleged "tech support," sometimes you want to
reboot the person.

Actually my first ISP was really good, albeit expensive.  If I dialled
in, and nothing seemed to work, I'd note down the IP I'd been assigned,
and send them an email about this when I did manage to log in.  I'd get
an email back acknowledging it, often saying they've checked on that
piece of their gear, and that they'd given it a reboot (it's often the
simplest thing to do, to unstick equipment).  If you were having
problems logging on, they'd ask you to dial a specific number, and
they'd watch the login.  Then they could tell you if your modem was
faulty, needed different AT settings, or you'd mistyped your
credentials.

I suppose one reason that they were so good, is that before they became
an ISP they were a computing consultancy firm.  Unfortunately, they got
bought out.

-- 
[tim@localhost ~]$ uname -rsvp
Linux 5.0.16-100.fc28.x86_64 #1 SMP Tue May 14 18:22:28 UTC 2019 x86_64

Boilerplate:  All mail to my mailbox is automatically deleted.
There is no point trying to privately email me, I only get to see
the messages posted to the mailing list.

Computers are like dentists.
They have their uses, but they're both bloody pains.

[home user]

>  After dealing with some alleged "tech support,"
>  sometimes you want to reboot the person. 
Hmmmm....
I could read that in more than one way!
:}

Modem reboots/resets are a pain.  Gotta hold a teeny, recessed button in 
for 30+ seconds; or unplug the modem, remove the battery, put the 
battery back in, and plug the modem back in.  Either way, it's then 15+ 
minutes for the thing to boot up.

My understanding is that the customer service reps are just following 
scripts (and "orders").  What's bad is the hard time they give me when I 
ask to escalate, and the high monthly fee I pay the ISP.  I wonder how 
much of that fee goes to the huge amount of advertising they do.

Then there's that almost universal tech support answer:
"We don't support Linux.".

Bill.

[Tim]

Tim:
> > After dealing with some alleged "tech support,"
> > sometimes you want to reboot the person. 
Bill:
>  Hmmmm....
>  I could read that in more than one way!
>  :} 
Exactly!


>  Modem reboots/resets are a pain.  Gotta hold a teeny, recessed
> button
>  in for 30+ seconds; or unplug the modem, remove the battery, put the 
>  battery back in, and plug the modem back in.  Either way, it's then
>  15+ minutes for the thing to boot up. 
No fun with me, either, with a fibre modem bolted on the wall a foot up
from the floor, with a tiny reset hole facing down (as well as all the
furniture in the way).  It's just about as hard to unplug its DC power
plug from the UPS (which has no off switch, at all).

Likewise there's a 10 minute wait before it comes alive, it's slow to
boot, and the ISP is slow to configure things.  Sometimes it won't
authenticate and you can go through a few reboots.  Our phone goes
through it, good luck if you needed to make an emergency call and had
to reset the box, first.  The phone used to go through the
modem/router, too, as VOIP, until I protested.  That added another 5
minute wait till you could use the phone.  And the modem/router had no
battery backup.

This was supposed to be progress!!!

>  My understanding is that the customer service reps are just
>  following scripts (and "orders").  What's bad is the hard time they
>  give me when I ask to escalate, and the high monthly fee I pay the
>  ISP. 
It's why I hate large ISPs.  The smaller ones generally don't have call
centres.  They have techs running the place, notice their own faults
soon, and know how to fix yours.

>  I wonder how much of that fee goes to the huge amount of advertising
>  they do. 
That would be no surprise.  In many businesses, the cost of the product
is often far less than the marketing.  Especially if its mass
marketing.  All our essential services are like that after they were
privatised, that just pushed prices through the roof, as they just
priced gouged everyone up to the point that people were willing to pay.

I was mind boggled by a news article trying to claim that privatisation
had pushed prices down, where elsewhere in the same article was a table
of prices showing how *everything* had gone up, very much. 
Unfortunately, we're too used to spin, but it's staggering to see
someone try and say one thing while providing contrary evidence.

>  Then there's that almost universal tech support answer:
>  "We don't support Linux.". 
Which, generally speaking, is easier to support.  The users tend to be
less clueless, and it's more a case of "tell me the info," rather than
"where do I type it in?"

-- 
[tim@localhost ~]$ uname -rsvp
Linux 5.0.16-100.fc28.x86_64 #1 SMP Tue May 14 18:22:28 UTC 2019 x86_64

Boilerplate:  All mail to my mailbox is automatically deleted.
There is no point trying to privately email me, I only get to see
the messages posted to the mailing list.

It seems the modern trend with Linux programmers is to change existing software
so that it's more annoying to use (e.g. making reboots required, when they
never used to be), then denying that *that* is a nuisance, then saying it's
necessary (ignoring that several years of prior versions didn't have that
stupid requirement), then complaining about being criticised for making things
worse.  Don't try giving me an Emperor's New Clothes routine, it won't wash.

[home user]

I've submitted Mozilla bug #1570092 to deal with this problem.