Arch Linux

mlopes

Member

Registered: 2018-05-04

Posts: 3

Odd behaviour after package update

Hi,

This morning I noticed one of my cores was at 100% usage, so I went to check what was causing it, and found this:

31714 mlopes    20   0  405560  26848  19800 R  97.7   0.2  34:34.25 firefox

I was a bit surprised, as I never use Firefox, so I'm 100% sure I didn't start it myself. I looked at the time the process had been running for, and saw that it started after I ran pacman -Syu.

I proceeded to kill the process:

kill -9 31714

And was surprised to see that as soon as I pressed enter on the kill comand, chromium opened itself, again I'm sure I didn't open it, as I use vimb for doing my web browsing.

Here's the list of packages that pacman updated this morning:

dhcpcd-7.0.4-1  docker-compose-1.21.2-1  file-5.33-1  libaio-0.3.111-1  libwbclient-4.8.1-1  pacman-5.0.2-3  rxvt-unicode-9.22-6  rxvt-unicode-terminfo-9.22-6  smbclient-4.8.1-1

.

Does anyone have any ideas of what could be going on?

Thanks,
Marco

mrunion

Member

From: Jonesborough, TN

Registered: 2007-01-26

Posts: 1,938

Website

Re: Odd behaviour after package update

So you said Firefox was running, you killed it, then Chromium opened again. Were both Firefox and Chromium running? Are the browsers trying to hit a specific URL, or are they just opened. Are they visible on the screen?

---

Matt

"It is very difficult to educate the educated."

x33a

Forum Fellow

Registered: 2009-08-15

Posts: 4,587

Re: Odd behaviour after package update

If you never use firefox, do you remember installing it yourself?

What is the output

pacman -Qi firefox

Also, what DE/WM are you using (just to know if some metapackage pulled firefox as a dependency).

mlopes

Member

Registered: 2018-05-04

Posts: 3

Re: Odd behaviour after package update

So you said Firefox was running, you killed it, then Chromium opened again

Again was after a coma as in "again, just as with Firefox it wasn't opened by myself.

Are the browsers trying to hit a specific URL, or are they just opened. Are they visible on the screen?

Firefox wasn't visible, I didn't check if it was trying to open an URL. When chromium opened, it was visible and went to the home screen, didn't open any URL.

If you never use firefox, do you remember installing it yourself?

What is the output

pacman -Qi firefox

Also, what DE/WM are you using (just to know if some metapackage pulled firefox as a dependency).

I did install Firefox myself a few months ago to test something, but haven't used it ever since.

x33a

Forum Fellow

Registered: 2009-08-15

Posts: 4,587

Re: Odd behaviour after package update

Can you confirm which browser is set as the default?

What's the output of

xdg-mime query default x-scheme-handler/http
xdg-mime query default x-scheme-handler/https
xdg-mime query default text/html

mlopes

Member

Registered: 2018-05-04

Posts: 3

Re: Odd behaviour after package update

Can you confirm which browser is set as the default?

What's the output of

xdg-mime query default x-scheme-handler/http
xdg-mime query default x-scheme-handler/https
xdg-mime query default text/html

The outpub of that is vimb for everything:

$ xdg-mime query default x-scheme-handler/http
                    xdg-mime query default x-scheme-handler/https
                    xdg-mime query default text/html
vimb.desktop
vimb.desktop
vimb.desktop

x33a

Forum Fellow

Registered: 2009-08-15

Posts: 4,587

Re: Odd behaviour after package update

Oh well, at this point it is really difficult to say what happened. Let us know if it happens again.