Chrome installation

[appye]

Hello, I am confused as to what is happening here. Look at the output of these installation commands for Chrome:

APT/APT-GET

Code: Select all

autumn@AutumnBigTop:~/Desktop$ sudo apt install ./google-chrome-stable_current_amd64.deb 
Reading package lists... Done
Building dependency tree       
Reading state information... Done
Note, selecting 'google-chrome-stable' instead of './google-chrome-stable_current_amd64.deb'
The following additional packages will be installed:
  libu2f-udev
The following NEW packages will be installed:
  google-chrome-stable libu2f-udev
0 upgraded, 2 newly installed, 0 to remove and 0 not upgraded.
Need to get 6,108 B/86.2 MB of archives.
After this operation, 272 MB of additional disk space will be used.
Do you want to continue? [Y/n] n
Abort.

• apt/apt-get installs libu2f-udev

• /usr/bin/apt search libu2f-udev shows the package as "installed, automatic"

• apt-get autoremove google-chrome-stable offers to remove libu2f-udev as well.

GDEBI

Code: Select all

sudo gdebi ./google-chrome-stable_current_amd64.deb 
Reading package lists... Done
Building dependency tree        
Reading state information... Done
Reading state information... Done
Requires the installation of the following packages: libgcc1

The web browser from Google
 Google Chrome is a browser that combines a minimal design with sophisticated technology to make the web faster, safer, and easier.
Do you want to install the software package? [y/N]:n

• gdebi installs libgcc1

• /usr/bin/apt search libgcc1 shows the package as "installed, automatic"

• apt-get autoremove google-chrome-stable does NOT offer to remove libgcc1

DPKG

Code: Select all

autumn@AutumnBigTop:~/Desktop$ sudo dpkg -i ./google-chrome-stable_current_amd64.deb 
Selecting previously unselected package google-chrome-stable.
(Reading database ... 285220 files and directories currently installed.)
Preparing to unpack .../google-chrome-stable_current_amd64.deb ...
Unpacking google-chrome-stable (92.0.4515.107-1) ...
Setting up google-chrome-stable (92.0.4515.107-1) ...
update-alternatives: using /usr/bin/google-chrome-stable to provide /usr/bin/x-www-browser (x-www-browser) in auto mode
update-alternatives: using /usr/bin/google-chrome-stable to provide /usr/bin/gnome-www-browser (gnome-www-browser) in auto mode
update-alternatives: using /usr/bin/google-chrome-stable to provide /usr/bin/google-chrome (google-chrome) in auto mode
Processing triggers for gnome-menus (3.36.0-1ubuntu1) ...
Processing triggers for desktop-file-utils (0.24+linuxmint1) ...
Processing triggers for mime-support (3.64ubuntu1) ...
Processing triggers for man-db (2.9.1-1) ...
autumn@AutumnBigTop:~/Desktop$ sudo apt-get -f install
Reading package lists... Done
Building dependency tree       
Reading state information... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
autumn@AutumnBigTop:~/Desktop$ 

• After installing with dpkg, apt-get -f install does not see anything broken

At first glance at least, Chrome seems to be working fine after any of these installs, with our without either of these dependencies. I have not noticed this differing behavior before, though I traditionally run vanilla Debian and use apt to install local .deb files. Apt is different on Mint and does not autocomplete the filename, which is what initially led me down this rabbit hole.

Does someone know what's going on? Which of these should I trust more?