Install Google Chrome in Fedora 32 Template

[799]

Hello,

I am trying to setup a multimedia AppVM based on a fedora-32-minimal template and want to install Chrome in the template VM.

Unfortunately I am unable to resolve dependencies to install the chrome.rpm-package.

I need to install libappindicator3.so.1()(64bit) and I am unable to find a way to install it from the default repo's.

https://rpmfind.net/linux/rpm2html/search.php?query=libappindicator3&submit=Search+...&system=&arch=

Any ideas how to do so?

[799]

[Frédéric Pierret]

$ dnf search libappindicator

Copr repo for fedy owned by kwizart 6.0 kB/s | 4.3 kB 00:00
Copr repo for PyCharm owned by phracek 82 kB/s | 71 kB 00:00
Fedora 32 openh264 (From Cisco) - x86_64 3.1 kB/s | 5.1 kB 00:01
Fedora Modular 32 - x86_64 1.2 MB/s | 4.9 MB 00:04
Fedora Modular 32 - x86_64 - Updates 2.0 MB/s | 3.7 MB 00:01
Fedora 32 - x86_64 - Updates 4.7 MB/s | 22 MB 00:04
Fedora 32 - x86_64 12 MB/s | 70 MB 00:05
Qubes OS Repository for VM (updates) 135 kB/s | 108 kB 00:00
================================================================================================================================================================================================== Name Exactly Matched: libappindicator ==================================================================================================================================================================================================
libappindicator.i686 : Application indicators library
libappindicator.x86_64 : Application indicators library
================================================================================================================================================================================================= Name & Summary Matched: libappindicator =================================================================================================================================================================================================
libappindicator-devel.i686 : Development files for libappindicator
libappindicator-devel.x86_64 : Development files for libappindicator
libappindicator-docs.noarch : Documentation for libappindicator and libappindicator-gtk3
libappindicator-gtk3-devel.i686 : Development files for libappindicator-gtk3
libappindicator-gtk3-devel.x86_64 : Development files for libappindicator-gtk3
libappindicator-sharp-devel.i686 : Development files for libappindicator-sharp
libappindicator-sharp-devel.x86_64 : Development files for libappindicator-sharp
====================================================================================================================================================================================================== Name Matched: libappindicator ======================================================================================================================================================================================================
libappindicator-gtk3.x86_64 : Application indicators library - GTK 3
libappindicator-gtk3.i686 : Application indicators library - GTK 3
libappindicator-sharp.x86_64 : Application indicators library - C#
==================================================================================================================================================================================================== Summary Matched: libappindicator =====================================================================================================================================================================================================
perl-Gtk2-AppIndicator.x86_64 : Perl extension for libappindicator


I'd bet it's into one of those?

> [799]
>
> --
> You received this message because you are subscribed to the Google Groups "qubes-users" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users...@googlegroups.com <mailto:qubes-users...@googlegroups.com>.
> To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/CAJ3yz2tVJ5rxhMfpv%3DFzQszjz_3mrvMmsPJ6WNyWK50Hrvh9vg%40mail.gmail.com <https://groups.google.com/d/msgid/qubes-users/CAJ3yz2tVJ5rxhMfpv%3DFzQszjz_3mrvMmsPJ6WNyWK50Hrvh9vg%40mail.gmail.com?utm_medium=email&utm_source=footer>.

[799]

Hello Frederic,

I found a much easier approach by enabling network connectivity during template customization and using Google's package repository.

This is fine for me, because my multimedia-AppVM will be declared as untrusted and is only used for specific "rich-media-tasks".

This is how I've setup my multimedia-AppVM from dom0:

Template=fedora-32-minimal
TemplateName=t-fedora-32-media
AppVMName=my-media
qvm-clone $Template $TemplateName

#Enable networking for template VM
qvm-prefs --set $TemplateName netvm sys-net

#Update Template
qvm-run --auto --pass-io --no-gui --user root $TemplateName \
  'dnf -y update'
qvm-run --auto --pass-io --no-gui --user root $TemplateName \
  'dnf -y install  qubes-usb-proxy pulseaudio-qubes qubes-core-agent-networking'

# Install Chrome

qvm-run --pass-io --no-gui --user root $TemplateName \
  'dnf install -y fedora-workstation-repositories && \
   dnf config-manager --set-enabled google-chrome && \
   dnf install -y google-chrome-stable'

#Disable networking for template VM
qvm-prefs --set $TemplateName netvm sys-net
qvm-shutdown --wait $TemplateName

# Create AppVM
qvm-create --template $TemplateName --label orange $AppVMName

Google Chrome can now be started via google-chrome from a terminal in the AppVM.

Of course you can also create a shortcut for the Qubes menu manually (it's in the Qubes Docs) pointing to /usr/bin/google-chrome

regards

799

[Frédéric Pierret]

Hi,

On 2020-09-09 09:51, 799 wrote:
> Hello Frederic,
>
> I found a much easier approach by enabling network connectivity during template customization and using Google's package repository.
> This is fine for me, because my multimedia-AppVM will be declared as untrusted and is only used for specific "rich-media-tasks".

At which step do you need to set netvm to your template?

Depending on requirements, maybe that can be adapted.

Best regards,
Frédéric