template and dependent qube show different behaviour

[Franz]

Hello friends,

I installed into Fedora 31 template a proprietary banking rpm application/plugin/extension which is supposed to work with the browsers during banking tasks. This is called warsaw_setup_fedora_64.rpm

When I start the dependent banking qubes a strange small window appears telling: "you must be logged in as root to install the proprietary packages". But the same window does not appear when I start the template where I installed the software.

So why is it that the template and the dependent qubes do not perform the same behavior?

Also, any idea to fix it, considering that the banking tasks cannot be done.

[dhorf-hfre...@hashmail.org]

On Thu, May 07, 2020 at 08:30:14AM -0300, Franz wrote:
> I installed into Fedora 31 template a proprietary banking rpm
> application/plugin/extension which is supposed to work with the browsers
> during banking tasks. This is called warsaw_setup_fedora_64.rpm

this sounds like a terrible idea unless you make a separate template
just for that task.

> So why is it that the template and the dependent qubes do not perform the
> same behavior?

check if it installed anything to /usr/local or /home.
rpm -ql warsaw_setup_fedora_64

> Also, any idea to fix it, considering that the banking tasks cannot be done.

i would probably just install it in a separate appvm from rc.local
this means no modification of the template at all, and the pkg gets
reinstalled everytime the appvm used for banking is started.

if that is viable depends very much on what that pkg and the software
it installs are actualy doing.

[haaber]

> On Thu, May 07, 2020 at 08:30:14AM -0300, Franz wrote:
>> I installed into Fedora 31 template a proprietary banking rpm
>> application/plugin/extension which is supposed to work with the browsers
>> during banking tasks. This is called warsaw_setup_fedora_64.rpm
>
> this sounds like a terrible idea unless you make a separate template
> just for that task.

I second that. What you could do, if you are space-limited for cloning
templateVM's is to install the *dependencies* of your app in the
template (using dnf yum, whatsoever) and then redo the "rpm install" of
the warsaw file in the appVM at each boot. With dep. solved that is
really fast.

[Franz]

On Thu, May 7, 2020 at 8:40 AM <dhorf-hfre...@hashmail.org> wrote:

On Thu, May 07, 2020 at 08:30:14AM -0300, Franz wrote:
> I installed into Fedora 31 template a proprietary banking rpm
> application/plugin/extension which is supposed to work with the browsers
> during banking tasks. This is called warsaw_setup_fedora_64.rpm

this sounds like a terrible idea unless you make a separate template
just for that task.

Thanks Dhorf, yes I made a separate template, do not trust this warsaw stuff

> So why is it that the template and the dependent qubes do not perform the
> same behavior?

check if it installed anything to /usr/local or /home.
rpm -ql warsaw_setup_fedora_64

your command clarified the situation, it tells: package warsaw_setup... is not installed.

In fact, after removing it and installing again found an installation error:

Failed to execute /usr/lib/systemd/systemd-sysv-install: No such file or directory

But this is not a Qubes specific problem, googling a bit it seems a problem with fedora 31.

> Also, any idea to fix it, considering that the banking tasks cannot be done.

i would probably just install it in a separate appvm from rc.local

I am not getting this. If I install it into a separate appvm, it will not ask me if I want it installed  from rc.local or otherwise.

this means no modification of the template at all, and the pkg gets
reinstalled everytime the appvm used for banking is started.

If it gets reinstalled automatically, it would be interesting not only for this warsaw thing.