Re: [qubes-users] trouble with apt-get on dabian

2021-03-02 Thread 'awokd' via qubes-users

Steve Coleman:


Apparently, I need to reinstall a new fedora-33 template baseline and
painstakingly install all these packages one at a time while restarting
Debian-10 to try an 'apt-get update' between package installs. Somewhere
along the way, it will break and whatever I just installed will be the
culprit. I think I'll be doing a lot of cloning of templates creating
checkpoints along the way.


Good find. Hope my suggestions didn't cost you too much time.

Depending how many packages you're talking about, a binary search might 
help- install half of them recursively.


--
- don't top post
Mailing list etiquette:
- trim quoted reply to only relevant portions
- when possible, copy and paste text instead of screenshots

--
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/3b78adc2-73b3-b0d2-58ac-f3f1b2227eca%40danwin1210.me.


Re: [qubes-users] trouble with apt-get on dabian

2021-03-02 Thread Mike Keehan

On 3/1/21 11:48 AM, Mike Keehan wrote:



HI,

Just a "me too" I'm afraid.  I installed Fedora 33, and used it for all
the sys-vms, and my sys-net would not connect to wifi - kept displaying
the prompt for the wifi password, even though the password was correct.

Switched back to Fedora 32 on sys-net, and it works OK again.

(I also had my screen freeze at one point - might be due to the i915
driver update.  Had this problem a long time ago when using the Arch
distro, but never on Qubes before.)

Just monitoring things for now.

Mike.



Did an update and now it works fine.  Silly me.

Mike.

--
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/0d3ee0e3-7353-3f84-654b-5bb776efdefd%40keehan.net.


Re: [qubes-users] trouble with apt-get on dabian

2021-03-01 Thread Kyss tfafm
The trouble you might be having (Mike) is that the switch possibly led to 
Network manager thinking that you had a whole other network connection 
(look for existing network connection & there is often simple fix) that is 
considered WiFi. The device is best set to the more generic MAC instead of 
the device name which can become different at the change (drop of a hat) of 
a template. However the default is often to grab the MAC plus the existing 
device name which leads to the problem.

On Monday, March 1, 2021 at 5:48:34 AM UTC-6 Mike Keehan wrote:

> On 3/1/21 5:05 AM, Steve Coleman wrote:
> > 
> > 
> > On Wed, Feb 24, 2021 at 5:49 AM 'awokd' via qubes-users 
> > mailto:qubes...@googlegroups.com>> wrote:
> > 
> > Steve Coleman:
> > 
> > > I installed the stock Debian-10 rpm yesterday and it also fails
> > to update
> > > using the default proxy. The whonix templates based on Debian
> > work because
> > > they are using a different update vm.
> > >
> > > I really don't have a clue how all the Fedora templates work
> > using the
> > > exact same default update proxy while the Debian ones do not. I
> > have not
> > > made any deliberate custom modifications to any of the update
> > settings, but
> > > something obviously changed.
> > >
> > > My suspicion is on the receiving side proxy configuration in
> > sys-firewall
> > > but I don't know how to debug that. With the TERM setting being
> > complained
> > > about I am wondering how this proxy is being launched without a
> > full set of
> > > environment variables. This error text is in red, as coming
> > through the
> > > pipe, so its on the other side, not in the template itself. The
> > update pipe
> > > is not a terminal afaik so I don't know why the proxy would be
> > complaining
> > > it doesn't know the terminal type. But then why does the Fedora
> > update
> > > still work and Debian not using the exact same update gateway.
> > Very odd.
> > >
> > I agree, sounds like something broken in sys-firewall given your other
> > UpdateVM is working. You could change your templates to use the same
> > UpdateVM as Whonix if you wanted to confirm. Otherwise, there's nothing
> > special about the sys-firewall AppVM. If you don't mind recreating any
> > firewall rules, try creating a new AppVM and confirm you don't get that
> > TERM warning at the terminal. Next, change anything that points to
> > sys-firewall for networking to the new one, and make it your new
> > UpdateVM?
> > 
> > 
> > There is a package in the Fedora distribution that is causing this 
> > problem. I switched both my sys-net and sys-firewall to use the new 
> > fedora-33 template that was just released and suddenly my Debian-10 
> > could update again. Then I started installing all the packages that I 
> > previously had in my fedora-32 template and suddenly my Debian-10 update 
> > is broken again.
> > 
> > I then tried to revert back by switching both sys-net/sys-firewall vm's 
> > to the fedora-33-minimal I had available but sys-net would not even boot 
> > up using minimal. Switching it again to a default fedora-32 allowed it 
> > to boot again. And sys-firewall blocked all network traffic using 
> > fedora-33-minimal so again I needed to revert that back to a default 
> > fedora-32 to get back online just to write this email.
> > 
> > Apparently, I need to reinstall a new fedora-33 template baseline and 
> > painstakingly install all these packages one at a time while restarting 
> > Debian-10 to try an 'apt-get update' between package installs. Somewhere 
> > along the way, it will break and whatever I just installed will be the 
> > culprit. I think I'll be doing a lot of cloning of templates creating 
> > checkpoints along the way.
> > 
> > Steve
> > 
>
> HI,
>
> Just a "me too" I'm afraid. I installed Fedora 33, and used it for all
> the sys-vms, and my sys-net would not connect to wifi - kept displaying
> the prompt for the wifi password, even though the password was correct.
>
> Switched back to Fedora 32 on sys-net, and it works OK again.
>
> (I also had my screen freeze at one point - might be due to the i915
> driver update. Had this problem a long time ago when using the Arch
> distro, but never on Qubes before.)
>
> Just monitoring things for now.
>
> Mike.
>
>

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/c9890c4b-0569-42e2-b400-b66d6a37bc63n%40googlegroups.com.


Re: [qubes-users] trouble with apt-get on dabian

2021-03-01 Thread Mike Keehan

On 3/1/21 5:05 AM, Steve Coleman wrote:



On Wed, Feb 24, 2021 at 5:49 AM 'awokd' via qubes-users 
mailto:qubes-users@googlegroups.com>> wrote:


Steve Coleman:

 > I installed the stock Debian-10 rpm yesterday and it also fails
to update
 > using the default proxy. The whonix templates based on Debian
work because
 > they are using a different update vm.
 >
 > I really don't have a clue how all the Fedora templates work
using the
 > exact same default update proxy while the Debian ones do not. I
have not
 > made any deliberate custom modifications to any of the update
settings, but
 > something obviously changed.
 >
 > My suspicion is on the receiving side proxy configuration in
sys-firewall
 > but I don't know how to debug that. With the TERM setting being
complained
 > about I am wondering how this proxy is being launched without a
full set of
 > environment variables. This error text is in red, as coming
through the
 > pipe, so its on the other side, not in the template itself. The
update pipe
 > is not a terminal afaik so I don't know why the proxy would be
complaining
 > it doesn't know the terminal type. But then why does the Fedora
update
 > still work and Debian not using the exact same update gateway.
Very odd.
 >
I agree, sounds like something broken in sys-firewall given your other
UpdateVM is working. You could change your templates to use the same
UpdateVM as Whonix if you wanted to confirm. Otherwise, there's nothing
special about the sys-firewall AppVM. If you don't mind recreating any
firewall rules, try creating a new AppVM and confirm you don't get that
TERM warning at the terminal. Next, change anything that points to
sys-firewall for networking to the new one, and make it your new
UpdateVM?


There is a package in the Fedora distribution that is causing this 
problem. I switched both my sys-net and sys-firewall to use the new 
fedora-33 template that was just released and suddenly my Debian-10 
could update again. Then I started installing all the packages that I 
previously had in my fedora-32 template and suddenly my Debian-10 update 
is broken again.


I then tried to revert back by switching both sys-net/sys-firewall vm's 
to the fedora-33-minimal I had available but sys-net would not even boot 
up using minimal. Switching it again to a default fedora-32 allowed it 
to boot again. And sys-firewall blocked all network traffic using 
fedora-33-minimal so again I needed to revert that back to a default 
fedora-32 to get back online just to write this email.


Apparently, I need to reinstall a new fedora-33 template baseline and 
painstakingly install all these packages one at a time while restarting 
Debian-10 to try an 'apt-get update' between package installs. Somewhere 
along the way, it will break and whatever I just installed will be the 
culprit. I think I'll be doing a lot of cloning of templates creating 
checkpoints along the way.


Steve



HI,

Just a "me too" I'm afraid.  I installed Fedora 33, and used it for all
the sys-vms, and my sys-net would not connect to wifi - kept displaying
the prompt for the wifi password, even though the password was correct.

Switched back to Fedora 32 on sys-net, and it works OK again.

(I also had my screen freeze at one point - might be due to the i915
driver update.  Had this problem a long time ago when using the Arch
distro, but never on Qubes before.)

Just monitoring things for now.

Mike.

--
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/2f806f50-138d-de28-837e-667a40ed0d06%40keehan.net.


Re: [qubes-users] trouble with apt-get on dabian

2021-02-28 Thread Steve Coleman
On Wed, Feb 24, 2021 at 5:49 AM 'awokd' via qubes-users <
qubes-users@googlegroups.com> wrote:

> Steve Coleman:
>
> > I installed the stock Debian-10 rpm yesterday and it also fails to update
> > using the default proxy. The whonix templates based on Debian work
> because
> > they are using a different update vm.
> >
> > I really don't have a clue how all the Fedora templates work using the
> > exact same default update proxy while the Debian ones do not. I have not
> > made any deliberate custom modifications to any of the update settings,
> but
> > something obviously changed.
> >
> > My suspicion is on the receiving side proxy configuration in sys-firewall
> > but I don't know how to debug that. With the TERM setting being
> complained
> > about I am wondering how this proxy is being launched without a full set
> of
> > environment variables. This error text is in red, as coming through the
> > pipe, so its on the other side, not in the template itself. The update
> pipe
> > is not a terminal afaik so I don't know why the proxy would be
> complaining
> > it doesn't know the terminal type. But then why does the Fedora update
> > still work and Debian not using the exact same update gateway. Very odd.
> >
> I agree, sounds like something broken in sys-firewall given your other
> UpdateVM is working. You could change your templates to use the same
> UpdateVM as Whonix if you wanted to confirm. Otherwise, there's nothing
> special about the sys-firewall AppVM. If you don't mind recreating any
> firewall rules, try creating a new AppVM and confirm you don't get that
> TERM warning at the terminal. Next, change anything that points to
> sys-firewall for networking to the new one, and make it your new UpdateVM?
>
>
There is a package in the Fedora distribution that is causing this problem.
I switched both my sys-net and sys-firewall to use the new fedora-33
template that was just released and suddenly my Debian-10 could update
again. Then I started installing all the packages that I previously had in
my fedora-32 template and suddenly my Debian-10 update is broken again.

I then tried to revert back by switching both sys-net/sys-firewall vm's to
the fedora-33-minimal I had available but sys-net would not even boot up
using minimal. Switching it again to a default fedora-32 allowed it to boot
again. And sys-firewall blocked all network traffic using fedora-33-minimal
so again I needed to revert that back to a default fedora-32 to get back
online just to write this email.

Apparently, I need to reinstall a new fedora-33 template baseline and
painstakingly install all these packages one at a time while restarting
Debian-10 to try an 'apt-get update' between package installs. Somewhere
along the way, it will break and whatever I just installed will be the
culprit. I think I'll be doing a lot of cloning of templates creating
checkpoints along the way.

Steve

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/CAJ5FDniYnZXOsB3-u7xJyxoPRapK0LD%3DA-TqmVj%2BBxa%2BbJi_XQ%40mail.gmail.com.


Re: [qubes-users] trouble with apt-get on dabian

2021-02-24 Thread 'awokd' via qubes-users

Steve Coleman:


I installed the stock Debian-10 rpm yesterday and it also fails to update
using the default proxy. The whonix templates based on Debian work because
they are using a different update vm.

I really don't have a clue how all the Fedora templates work using the
exact same default update proxy while the Debian ones do not. I have not
made any deliberate custom modifications to any of the update settings, but
something obviously changed.

My suspicion is on the receiving side proxy configuration in sys-firewall
but I don't know how to debug that. With the TERM setting being complained
about I am wondering how this proxy is being launched without a full set of
environment variables. This error text is in red, as coming through the
pipe, so its on the other side, not in the template itself. The update pipe
is not a terminal afaik so I don't know why the proxy would be complaining
it doesn't know the terminal type. But then why does the Fedora update
still work and Debian not using the exact same update gateway. Very odd.

I agree, sounds like something broken in sys-firewall given your other 
UpdateVM is working. You could change your templates to use the same 
UpdateVM as Whonix if you wanted to confirm. Otherwise, there's nothing 
special about the sys-firewall AppVM. If you don't mind recreating any 
firewall rules, try creating a new AppVM and confirm you don't get that 
TERM warning at the terminal. Next, change anything that points to 
sys-firewall for networking to the new one, and make it your new UpdateVM?


--
- don't top post
Mailing list etiquette:
- trim quoted reply to only relevant portions
- when possible, copy and paste text instead of screenshots

--
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/d4fc7d1d-e1b2-0f10-a127-a104fe627636%40danwin1210.me.


Re: [qubes-users] trouble with apt-get on dabian

2021-02-23 Thread Steve Coleman
On Tue, Feb 23, 2021, 4:17 AM 'awokd' via qubes-users <
qubes-users@googlegroups.com> wrote:

> Steve Coleman:
> > I have a somewhat confusing issue with debian-10 updates and would like
> any
> > suggestions on where to look.
> >
> > All my fedora templates update just fine. Dom0 updates but it gives some
> > errors through the return pipe.
> >
> > can't get terminal type, defaulting to vt100.
> > please set the TERM env variable.
>
> I wonder if your Debian template is messed up somehow, and/or your
> Updatevm (can be determined by looking at qubes-prefs). If you open a
> regular terminal session on either, do you get that same warning?


It gives this warning/failure from both the qubes manager update and from
the command line in the template.

If so,
> you could temporarily switch your UpdateVM's template to Fedora and
> attempt an update.


It's already using the default Fedora temolate, and all the Fedora
templates work just fine using the exact same update VM (sys-firewall)


itself, there's probably a more subtle fix but I would switch my AppVMs
> over to Fedora, delete & reinstall a fresh copy of the Debian template,
> then switch them back.
>

I installed the stock Debian-10 rpm yesterday and it also fails to update
using the default proxy. The whonix templates based on Debian work because
they are using a different update vm.

I really don't have a clue how all the Fedora templates work using the
exact same default update proxy while the Debian ones do not. I have not
made any deliberate custom modifications to any of the update settings, but
something obviously changed.

My suspicion is on the receiving side proxy configuration in sys-firewall
but I don't know how to debug that. With the TERM setting being complained
about I am wondering how this proxy is being launched without a full set of
environment variables. This error text is in red, as coming through the
pipe, so its on the other side, not in the template itself. The update pipe
is not a terminal afaik so I don't know why the proxy would be complaining
it doesn't know the terminal type. But then why does the Fedora update
still work and Debian not using the exact same update gateway. Very odd.

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/CAJ5FDnjSpG3DsuQ83bDvQ67SCOoqKF6M3hAat3VYTNkYJ7xtXg%40mail.gmail.com.


Re: [qubes-users] trouble with apt-get on dabian

2021-02-23 Thread 'awokd' via qubes-users

Steve Coleman:

I have a somewhat confusing issue with debian-10 updates and would like any
suggestions on where to look.

All my fedora templates update just fine. Dom0 updates but it gives some
errors through the return pipe.

can't get terminal type, defaulting to vt100.
please set the TERM env variable.


I wonder if your Debian template is messed up somehow, and/or your 
Updatevm (can be determined by looking at qubes-prefs). If you open a 
regular terminal session on either, do you get that same warning? If so, 
you could temporarily switch your UpdateVM's template to Fedora and 
attempt an update. If the issue still occurs and it's with the template 
itself, there's probably a more subtle fix but I would switch my AppVMs 
over to Fedora, delete & reinstall a fresh copy of the Debian template, 
then switch them back.


--
- don't top post
Mailing list etiquette:
- trim quoted reply to only relevant portions
- when possible, copy and paste text instead of screenshots

--
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/689ffe55-e72e-8383-ed16-49fcd24f77bc%40danwin1210.me.