Budgie Welcome Google Chrome install doesnt work

I have just installed ubuntuBudgie.

First thing was to use welcome screen, and install the same internet browser i use on my windows and my android Screenshot from 2020-01-23 10-38-04 , but after pressing and confirming repo, it shortly fails https://i.imgur.com/6UsC5tg.png

My first impressions with ubuntuBudgie for now is, it is broken.

How do i fix this?

Please run in a terminal:

sudo apt update 
budgie-welcome

Then navigate to getting started - and try to install chrome again.

What is the output from running the two commands above?

Hi fossfreedom,

thank you kindly for responding so fast.

As you suggested i have run commands you listed…below is the output:

dado023@linux:~$ sudo apt update
[sudo] password for dado023: 
Hit:1 http://hr.archive.ubuntu.com/ubuntu eoan InRelease
Hit:2 http://hr.archive.ubuntu.com/ubuntu eoan-updates InRelease
Get:3 http://security.ubuntu.com/ubuntu eoan-security InRelease [97,5 kB]
Ign:4 http://dl.google.com/linux/chrome/deb stable InRelease                   
Hit:5 http://hr.archive.ubuntu.com/ubuntu eoan-backports InRelease             
Get:6 http://dl.google.com/linux/chrome/deb stable Release [943 B]
Get:7 http://dl.google.com/linux/chrome/deb stable Release.gpg [819 B]
Get:8 http://dl.google.com/linux/chrome/deb stable/main amd64 Packages [1.110 B]
Fetched 100 kB in 2s (59,2 kB/s)      
Reading package lists... Done
Building dependency tree       
Reading state information... Done
All packages are up-to-date.
dado023@linux:~$ budgie-welcome
error: no matching snaps installed
error: no matching snaps installed
error: no matching snaps installed
error: no matching snaps installed
error: no matching snaps installed
error: no matching snaps installed
error: no matching snaps installed
error: no matching snaps installed
error: no matching snaps installed
error: no matching snaps installed
/snap/ubuntu-budgie-welcome/145/usr/bin/budgie-welcome:651: PyGTKDeprecationWarning: Using positional arguments with the GObject constructor has been deprecated. Please specify keyword(s) for "parent, flags, message_type, buttons, message_format" or use a class specific constructor. See: https://wiki.gnome.org/PyGObject/InitializerDeprecations
  _("Third-Party Repositories"))
/snap/ubuntu-budgie-welcome/145/usr/bin/budgie-welcome:651: PyGTKDeprecationWarning: The keyword(s) "message_format" have been deprecated in favor of "text" respectively. See: https://wiki.gnome.org/PyGObject/InitializerDeprecations
  _("Third-Party Repositories"))
/snap/ubuntu-budgie-welcome/145/usr/bin/budgie-welcome:651: PyGTKDeprecationWarning: The "flags" argument for dialog construction is deprecated. Please use initializer keywords: modal=True and/or destroy_with_parent=True. See: https://wiki.gnome.org/PyGObject/InitializerDeprecations
  _("Third-Party Repositories"))
/snap/ubuntu-budgie-welcome/145/usr/lib/budgie-welcome/budgie-welcome-privileged-actions:193: DeprecationWarning: dist() and linux_distribution() functions are deprecated in Python 3.5
  release_code = platform.dist()[2]    # → xenial, yakkety, zesty
/snap/ubuntu-budgie-welcome/145/usr/lib/budgie-welcome/budgie-welcome-privileged-actions:84: DeprecationWarning: dist() and linux_distribution() functions are deprecated in Python 3.5
  release_code = platform.dist()[2]    # → xenial, yakkety, zesty
OK
Reading package lists... Done
Building dependency tree       
Reading state information... Done
The following NEW packages will be installed
  google-chrome-stable
0 to upgrade, 1 to newly install, 0 to remove and 0 not to upgrade.
Need to get 62,2 MB of archives.
After this operation, 221 MB of additional disk space will be used.
Get:1 http://dl.google.com/linux/chrome/deb stable/main amd64 google-chrome-stable amd64 79.0.3945.130-1 [62,2 MB]
Fetched 62,2 MB in 6s (9.713 kB/s)                                             
Selecting previously unselected package google-chrome-stable.
(Reading database ... 240998 files and directories currently installed.)
Preparing to unpack .../google-chrome-stable_79.0.3945.130-1_amd64.deb ...
Unpacking google-chrome-stable (79.0.3945.130-1) ...
Setting up google-chrome-stable (79.0.3945.130-1) ...
update-alternatives: using /usr/bin/google-chrome-stable to provide /usr/bin/x-w
ww-browser (x-www-browser) in auto mode
update-alternatives: using /usr/bin/google-chrome-stable to provide /usr/bin/gno
me-www-browser (gnome-www-browser) in auto mode
update-alternatives: using /usr/bin/google-chrome-stable to provide /usr/bin/goo
gle-chrome (google-chrome) in auto mode
Processing triggers for mime-support (3.63ubuntu1) ...
Processing triggers for gnome-menus (3.32.0-1ubuntu1) ...
Processing triggers for man-db (2.8.7-3) ...
Processing triggers for bamfdaemon (0.5.3+18.04.20180207.2-0ubuntu1) ...
Rebuilding /usr/share/applications/bamf-2.index...
Processing triggers for desktop-file-utils (0.24-1ubuntu1) ...
[Apt] Reloading cache... 
[Apt] Cache reloaded. 
error: no matching snaps installed
error: no matching snaps installed
error: no matching snaps installed
error: no matching snaps installed
error: no matching snaps installed

This seems to fix it, but still i would like to point out how important first experience is, especially because Budgie Welcome is the first point from which new user starts to setup his OS.

Once again, thank you.
Dan

Agree with you. Think possibly testing if the first time a failure occurs then forcing an apt update and rerunning the install might help here. Should be a relatively python based tweak if anyone has the time to do:

GitHub - UbuntuBudgie/budgie-welcome: Welcome app for Ubuntu Budgie

Which files would need to be changed? I could do it soon

Hey @fossfreedom - in bash I usuallt run this to see if my cache is older than 12 hours…

# Update APT Repos of older than 12 hours
if [ -z "$(find /var/cache/apt/pkgcache.bin -mmin -720)" ]; then
 sudo apt update
fi

So maybe an approach might be to simply check if this file exists at launch. and run an update if the file is older than say 24 hours?

or

Or an easy way might be to touch a file on first run after checking for -existence saves a bunch opf error checking logic.

Thoughts on these approaches?

Granted one os more elegant than the other. :slight_smile:

Hi why did you not just transfer your google chrome browser bar over to your os i did this on budgie/linux mint/peppermint/ systems