Re: [qubes-users] Kali VM no longer responding
Hello, thank you very much for the detailed answer. best regards J. Eppler -- 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 post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/fb7c8d91-00fb-4e45-8598-a950eab349ff%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Kali VM no longer responding
J. Eppler: > Hello @qubenix, > > I am interested in your Kali installation process. Did you run into any > trouble during the installation? Did you follow the KaliVM installation > instructions: https://www.qubes-os.org/doc/pentesting/kali/? > > regards > j. Eppler > Yes, followed the instructions from documentation until it came to package installation. I *did not* attempt to install kali-linux-full, use katoolin script, or any similar. I just install the packages as I need to keep it minimal. Basically I have a debian-9 VM with Kali repos added. I also have a Kali i386 image that I will run in a standalone HVM when I need to debug a 32 bit package. Although just yesterday I learned of `dpkg --add-architecture i386`, which I had to do to my debian-9/Kali template to get wine32. So now I may be able to do everything in just one AppVM. In summation, I've successfully followed both sets of instructions in the Qubes docs, but skipped steps 6 and 11 in the "Create Debian Based Kali Template" section and modified step 10 to only pull in the packages I need. -- qubenix GPG: B536812904D455B491DCDCDD04BE1E61A3C2E500 -- 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 post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/d468f312-d6de-4d9d-8b6d-91aa8abb8a09%40riseup.net. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Kali VM no longer responding
Hello @qubenix, I am interested in your Kali installation process. Did you run into any trouble during the installation? Did you follow the KaliVM installation instructions: https://www.qubes-os.org/doc/pentesting/kali/? regards j. Eppler -- 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 post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/4a7b9915-e2c3-42c4-8b24-1c338d5a5063%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Kali VM no longer responding
On Tuesday, December 13, 2016 at 1:22:51 AM UTC+1, qubenix wrote:
> qubenix:
> > Marek Marczykowski-Górecki:
> >> On Mon, Dec 12, 2016 at 05:10:00PM +, qubenix wrote:
> >>> Marek Marczykowski-Górecki:
> Looks like this issue:
> https://github.com/QubesOS/qubes-issues/issues/2514
>
> Rebuilt package just uploaded to testing repository
> (qubes-gui-agent_3.2.10-2+deb9u1).
>
>
> >>
> >>> Doesn't seem to be fixed in stretch, stretch-testing, or
> >>> stretch-securitytesting yet.
> >>
> >>> ```
> >>> [user@dom0 ~]$ qvm-run -p d9 "sudo apt-get update && sudo apt-get
> >>> dist-upgrade -y"
> >>> Hit:1 http://vwakviie2ienjx6t.onion/debian stretch InRelease
> >>> Hit:2 http://sgvtcaew4bxjd7ln.onion stretch/updates InRelease
> >>> Hit:3 http://deb.qubes-os.org/r3.2/vm stretch-testing InRelease
> >>> Hit:4 http://deb.qubes-os.org/r3.2/vm stretch-securitytesting InRelease
> >>> Reading package lists...
> >>> Reading package lists...
> >>> Building dependency tree...
> >>> Reading state information...
> >>> Calculating upgrade...
> >>> 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
> >>> [user@dom0 ~]$ qvm-run -p d9 "sudo dpkg -l" | grep qubes-gui
> >>> ii qubes-gui-agent 3.2.8+deb9u1 amd64 Makes X11 windows available to
> >>> qubes dom0
> >>> ```
> >>
> >> Interesting, I have qubes-gui-agent 3.2.11 already, from
> >> stretch-testing. Do you have some caching proxy in between?
> >>
> > At one point I was using Rustybirds update cache proxy, but I've since
> > switched back to a whonix-gw and unchecked "Allow connections to Updates
> > Proxy".
> >
> > I have two debian-9 templates, and they both were connected to update
> > cache and are now connected to whonix-gw. Here's the results from my two
> > debian-9 templates (one is using stretch-testing and
> > stretch-securitytesting the other has only stretch-testing although I
> > don't think that should matter):
> >
> > ```
> > [user@dom0 ~]$ qvm-run -p d9 "sudo apt-get update && sudo apt-get
> > dist-upgrade -y -V"
> > Hit:1 http://vwakviie2ienjx6t.onion/debian stretch InRelease
> > Hit:2 http://sgvtcaew4bxjd7ln.onion stretch/updates InRelease
> > Hit:3 http://deb.qubes-os.org/r3.2/vm stretch-testing InRelease
> > Hit:4 http://deb.qubes-os.org/r3.2/vm stretch-securitytesting InRelease
> > Reading package lists...
> > Reading package lists...
> > Building dependency tree...
> > Reading state information...
> > Calculating upgrade...
> > 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
> > [user@dom0 ~]$ qvm-run -p d9-kali "sudo apt-get update && sudo apt-get
> > dist-upgrade -y -V"
> > Hit:1 http://vwakviie2ienjx6t.onion/debian stretch InRelease
> > Hit:2 http://sgvtcaew4bxjd7ln.onion stretch/updates InRelease
> > Hit:3 http://deb.qubes-os.org/r3.2/vm stretch-testing InRelease
> > Hit:5 http://deb.bitmask.net/debian stretch InRelease
> > Hit:4 http://archive-3.kali.org/kali kali-rolling InRelease
> > Reading package lists...
> > Reading package lists...
> > Building dependency tree...
> > Reading state information...
> > Calculating upgrade...
> > The following packages have been kept back:
> >qubes-gui-agent (3.2.8+deb9u1 => 3.2.11-1+deb9u1)
> > 0 upgraded, 0 newly installed, 0 to remove and 1 not upgraded.
> > [user@dom0 ~]$ qvm-run -p d9-kali "sudo aptitude dist-upgrade"
> > Reading package lists...
> > Building dependency tree...
> > Reading state information...
> > Reading extended state information...
> > Initializing package states...
> > Building tag database...
> > The following NEW packages will be installed:
> > xserver-xorg-input-qubes{ab} xserver-xorg-video-dummyqbs{ab}
> > The following packages will be upgraded:
> > qubes-gui-agent
> > 1 packages upgraded, 2 newly installed, 0 to remove and 0 not upgraded.
> > Need to get 66.5 kB of archives. After unpacking 36.9 kB will be used.
> > The following packages have unmet dependencies:
> > xserver-xorg-video-dummyqbs : Depends: xorg-video-abi-23 which is a
> > virtual package, provided by:
> > - xserver-xorg-core
> > (2:1.19.0-2), but 2:1.18.4-2 is installed
> >
> >Depends: xserver-xorg-core (>=
> > 2:1.18.99.901) but 2:1.18.4-2 is installed
> > xserver-xorg-input-qubes : Depends: xorg-input-abi-24 which is a
> > virtual package, provided by:
> > - xserver-xorg-core (2:1.19.0-2),
> > but 2:1.18.4-2 is installed
> >
> > Depends: xserver-xorg-core (>=
> > 2:1.18.99.901) but 2:1.18.4-2 is installed
> > The following actions will resolve these dependencies:
> >
> > Keep the following packages at their current version:
> > 1) qubes-gui-agent [3.2.8+deb9u1 (now)]
> > 2) xserver-xorg-input-qubes [Not Installed]
> > 3) xserver-xorg-video-dummyqbs [Not Installed]
> >
> >
> >
> > Accept this solution? [Y/n/q/?]
> > ```
> >
> I fixed the second template (d9-kali) by issuing:
>
> s
Re: [qubes-users] Kali VM no longer responding
qubenix:
> qubenix:
>> Marek Marczykowski-Górecki:
>>> On Mon, Dec 12, 2016 at 05:10:00PM +, qubenix wrote:
Marek Marczykowski-Górecki:
> Looks like this issue:
> https://github.com/QubesOS/qubes-issues/issues/2514
>
> Rebuilt package just uploaded to testing repository
> (qubes-gui-agent_3.2.10-2+deb9u1).
>
>
>>>
Doesn't seem to be fixed in stretch, stretch-testing, or
stretch-securitytesting yet.
>>>
```
[user@dom0 ~]$ qvm-run -p d9 "sudo apt-get update && sudo apt-get
dist-upgrade -y"
Hit:1 http://vwakviie2ienjx6t.onion/debian stretch InRelease
Hit:2 http://sgvtcaew4bxjd7ln.onion stretch/updates InRelease
Hit:3 http://deb.qubes-os.org/r3.2/vm stretch-testing InRelease
Hit:4 http://deb.qubes-os.org/r3.2/vm stretch-securitytesting InRelease
Reading package lists...
Reading package lists...
Building dependency tree...
Reading state information...
Calculating upgrade...
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
[user@dom0 ~]$ qvm-run -p d9 "sudo dpkg -l" | grep qubes-gui
ii qubes-gui-agent 3.2.8+deb9u1 amd64 Makes X11 windows available to
qubes dom0
```
>>>
>>> Interesting, I have qubes-gui-agent 3.2.11 already, from
>>> stretch-testing. Do you have some caching proxy in between?
>>>
>> At one point I was using Rustybirds update cache proxy, but I've since
>> switched back to a whonix-gw and unchecked "Allow connections to Updates
>> Proxy".
>>
>> I have two debian-9 templates, and they both were connected to update
>> cache and are now connected to whonix-gw. Here's the results from my two
>> debian-9 templates (one is using stretch-testing and
>> stretch-securitytesting the other has only stretch-testing although I
>> don't think that should matter):
>>
>> ```
>> [user@dom0 ~]$ qvm-run -p d9 "sudo apt-get update && sudo apt-get
>> dist-upgrade -y -V"
>> Hit:1 http://vwakviie2ienjx6t.onion/debian stretch InRelease
>> Hit:2 http://sgvtcaew4bxjd7ln.onion stretch/updates InRelease
>> Hit:3 http://deb.qubes-os.org/r3.2/vm stretch-testing InRelease
>> Hit:4 http://deb.qubes-os.org/r3.2/vm stretch-securitytesting InRelease
>> Reading package lists...
>> Reading package lists...
>> Building dependency tree...
>> Reading state information...
>> Calculating upgrade...
>> 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
>> [user@dom0 ~]$ qvm-run -p d9-kali "sudo apt-get update && sudo apt-get
>> dist-upgrade -y -V"
>> Hit:1 http://vwakviie2ienjx6t.onion/debian stretch InRelease
>> Hit:2 http://sgvtcaew4bxjd7ln.onion stretch/updates InRelease
>> Hit:3 http://deb.qubes-os.org/r3.2/vm stretch-testing InRelease
>> Hit:5 http://deb.bitmask.net/debian stretch InRelease
>> Hit:4 http://archive-3.kali.org/kali kali-rolling InRelease
>> Reading package lists...
>> Reading package lists...
>> Building dependency tree...
>> Reading state information...
>> Calculating upgrade...
>> The following packages have been kept back:
>>qubes-gui-agent (3.2.8+deb9u1 => 3.2.11-1+deb9u1)
>> 0 upgraded, 0 newly installed, 0 to remove and 1 not upgraded.
>> [user@dom0 ~]$ qvm-run -p d9-kali "sudo aptitude dist-upgrade"
>> Reading package lists...
>> Building dependency tree...
>> Reading state information...
>> Reading extended state information...
>> Initializing package states...
>> Building tag database...
>> The following NEW packages will be installed:
>> xserver-xorg-input-qubes{ab} xserver-xorg-video-dummyqbs{ab}
>> The following packages will be upgraded:
>> qubes-gui-agent
>> 1 packages upgraded, 2 newly installed, 0 to remove and 0 not upgraded.
>> Need to get 66.5 kB of archives. After unpacking 36.9 kB will be used.
>> The following packages have unmet dependencies:
>> xserver-xorg-video-dummyqbs : Depends: xorg-video-abi-23 which is a
>> virtual package, provided by:
>> - xserver-xorg-core
>> (2:1.19.0-2), but 2:1.18.4-2 is installed
>>
>>Depends: xserver-xorg-core (>=
>> 2:1.18.99.901) but 2:1.18.4-2 is installed
>> xserver-xorg-input-qubes : Depends: xorg-input-abi-24 which is a
>> virtual package, provided by:
>> - xserver-xorg-core (2:1.19.0-2),
>> but 2:1.18.4-2 is installed
>>
>> Depends: xserver-xorg-core (>=
>> 2:1.18.99.901) but 2:1.18.4-2 is installed
>> The following actions will resolve these dependencies:
>>
>> Keep the following packages at their current version:
>> 1) qubes-gui-agent [3.2.8+deb9u1 (now)]
>> 2) xserver-xorg-input-qubes [Not Installed]
>> 3) xserver-xorg-video-dummyqbs [Not Installed]
>>
>>
>>
>> Accept this solution? [Y/n/q/?]
>> ```
>>
> I fixed the second template (d9-kali) by issuing:
>
> sudo apt-get install -t stretch xserver-xorg-core
> sudo apt-get dist-upgrade
>
> That fixed my dependency problem and upgraded/installed the 3 packages.
> Still, though, my d
Re: [qubes-users] Kali VM no longer responding
qubenix:
> Marek Marczykowski-Górecki:
>> On Mon, Dec 12, 2016 at 05:10:00PM +, qubenix wrote:
>>> Marek Marczykowski-Górecki:
Looks like this issue:
https://github.com/QubesOS/qubes-issues/issues/2514
Rebuilt package just uploaded to testing repository
(qubes-gui-agent_3.2.10-2+deb9u1).
>>
>>> Doesn't seem to be fixed in stretch, stretch-testing, or
>>> stretch-securitytesting yet.
>>
>>> ```
>>> [user@dom0 ~]$ qvm-run -p d9 "sudo apt-get update && sudo apt-get
>>> dist-upgrade -y"
>>> Hit:1 http://vwakviie2ienjx6t.onion/debian stretch InRelease
>>> Hit:2 http://sgvtcaew4bxjd7ln.onion stretch/updates InRelease
>>> Hit:3 http://deb.qubes-os.org/r3.2/vm stretch-testing InRelease
>>> Hit:4 http://deb.qubes-os.org/r3.2/vm stretch-securitytesting InRelease
>>> Reading package lists...
>>> Reading package lists...
>>> Building dependency tree...
>>> Reading state information...
>>> Calculating upgrade...
>>> 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
>>> [user@dom0 ~]$ qvm-run -p d9 "sudo dpkg -l" | grep qubes-gui
>>> ii qubes-gui-agent 3.2.8+deb9u1 amd64 Makes X11 windows available to
>>> qubes dom0
>>> ```
>>
>> Interesting, I have qubes-gui-agent 3.2.11 already, from
>> stretch-testing. Do you have some caching proxy in between?
>>
> At one point I was using Rustybirds update cache proxy, but I've since
> switched back to a whonix-gw and unchecked "Allow connections to Updates
> Proxy".
>
> I have two debian-9 templates, and they both were connected to update
> cache and are now connected to whonix-gw. Here's the results from my two
> debian-9 templates (one is using stretch-testing and
> stretch-securitytesting the other has only stretch-testing although I
> don't think that should matter):
>
> ```
> [user@dom0 ~]$ qvm-run -p d9 "sudo apt-get update && sudo apt-get
> dist-upgrade -y -V"
> Hit:1 http://vwakviie2ienjx6t.onion/debian stretch InRelease
> Hit:2 http://sgvtcaew4bxjd7ln.onion stretch/updates InRelease
> Hit:3 http://deb.qubes-os.org/r3.2/vm stretch-testing InRelease
> Hit:4 http://deb.qubes-os.org/r3.2/vm stretch-securitytesting InRelease
> Reading package lists...
> Reading package lists...
> Building dependency tree...
> Reading state information...
> Calculating upgrade...
> 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
> [user@dom0 ~]$ qvm-run -p d9-kali "sudo apt-get update && sudo apt-get
> dist-upgrade -y -V"
> Hit:1 http://vwakviie2ienjx6t.onion/debian stretch InRelease
> Hit:2 http://sgvtcaew4bxjd7ln.onion stretch/updates InRelease
> Hit:3 http://deb.qubes-os.org/r3.2/vm stretch-testing InRelease
> Hit:5 http://deb.bitmask.net/debian stretch InRelease
> Hit:4 http://archive-3.kali.org/kali kali-rolling InRelease
> Reading package lists...
> Reading package lists...
> Building dependency tree...
> Reading state information...
> Calculating upgrade...
> The following packages have been kept back:
>qubes-gui-agent (3.2.8+deb9u1 => 3.2.11-1+deb9u1)
> 0 upgraded, 0 newly installed, 0 to remove and 1 not upgraded.
> [user@dom0 ~]$ qvm-run -p d9-kali "sudo aptitude dist-upgrade"
> Reading package lists...
> Building dependency tree...
> Reading state information...
> Reading extended state information...
> Initializing package states...
> Building tag database...
> The following NEW packages will be installed:
> xserver-xorg-input-qubes{ab} xserver-xorg-video-dummyqbs{ab}
> The following packages will be upgraded:
> qubes-gui-agent
> 1 packages upgraded, 2 newly installed, 0 to remove and 0 not upgraded.
> Need to get 66.5 kB of archives. After unpacking 36.9 kB will be used.
> The following packages have unmet dependencies:
> xserver-xorg-video-dummyqbs : Depends: xorg-video-abi-23 which is a
> virtual package, provided by:
> - xserver-xorg-core
> (2:1.19.0-2), but 2:1.18.4-2 is installed
>
>Depends: xserver-xorg-core (>=
> 2:1.18.99.901) but 2:1.18.4-2 is installed
> xserver-xorg-input-qubes : Depends: xorg-input-abi-24 which is a
> virtual package, provided by:
> - xserver-xorg-core (2:1.19.0-2),
> but 2:1.18.4-2 is installed
>
> Depends: xserver-xorg-core (>=
> 2:1.18.99.901) but 2:1.18.4-2 is installed
> The following actions will resolve these dependencies:
>
> Keep the following packages at their current version:
> 1) qubes-gui-agent [3.2.8+deb9u1 (now)]
> 2) xserver-xorg-input-qubes [Not Installed]
> 3) xserver-xorg-video-dummyqbs [Not Installed]
>
>
>
> Accept this solution? [Y/n/q/?]
> ```
>
I fixed the second template (d9-kali) by issuing:
sudo apt-get install -t stretch xserver-xorg-core
sudo apt-get dist-upgrade
That fixed my dependency problem and upgraded/installed the 3 packages.
Still, though, my d9 template is acting as though there is no package to
upgrade.
--
qubenix
GPG: B536812904D455B491DCDCDD04BE1E61A3C2E500
--
Yo
Re: [qubes-users] Kali VM no longer responding
Marek Marczykowski-Górecki:
> On Mon, Dec 12, 2016 at 05:10:00PM +, qubenix wrote:
>> Marek Marczykowski-Górecki:
>>> Looks like this issue:
>>> https://github.com/QubesOS/qubes-issues/issues/2514
>>>
>>> Rebuilt package just uploaded to testing repository
>>> (qubes-gui-agent_3.2.10-2+deb9u1).
>>>
>>>
>
>> Doesn't seem to be fixed in stretch, stretch-testing, or
>> stretch-securitytesting yet.
>
>> ```
>> [user@dom0 ~]$ qvm-run -p d9 "sudo apt-get update && sudo apt-get
>> dist-upgrade -y"
>> Hit:1 http://vwakviie2ienjx6t.onion/debian stretch InRelease
>> Hit:2 http://sgvtcaew4bxjd7ln.onion stretch/updates InRelease
>> Hit:3 http://deb.qubes-os.org/r3.2/vm stretch-testing InRelease
>> Hit:4 http://deb.qubes-os.org/r3.2/vm stretch-securitytesting InRelease
>> Reading package lists...
>> Reading package lists...
>> Building dependency tree...
>> Reading state information...
>> Calculating upgrade...
>> 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
>> [user@dom0 ~]$ qvm-run -p d9 "sudo dpkg -l" | grep qubes-gui
>> ii qubes-gui-agent 3.2.8+deb9u1 amd64 Makes X11 windows available to
>> qubes dom0
>> ```
>
> Interesting, I have qubes-gui-agent 3.2.11 already, from
> stretch-testing. Do you have some caching proxy in between?
>
At one point I was using Rustybirds update cache proxy, but I've since
switched back to a whonix-gw and unchecked "Allow connections to Updates
Proxy".
I have two debian-9 templates, and they both were connected to update
cache and are now connected to whonix-gw. Here's the results from my two
debian-9 templates (one is using stretch-testing and
stretch-securitytesting the other has only stretch-testing although I
don't think that should matter):
```
[user@dom0 ~]$ qvm-run -p d9 "sudo apt-get update && sudo apt-get
dist-upgrade -y -V"
Hit:1 http://vwakviie2ienjx6t.onion/debian stretch InRelease
Hit:2 http://sgvtcaew4bxjd7ln.onion stretch/updates InRelease
Hit:3 http://deb.qubes-os.org/r3.2/vm stretch-testing InRelease
Hit:4 http://deb.qubes-os.org/r3.2/vm stretch-securitytesting InRelease
Reading package lists...
Reading package lists...
Building dependency tree...
Reading state information...
Calculating upgrade...
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
[user@dom0 ~]$ qvm-run -p d9-kali "sudo apt-get update && sudo apt-get
dist-upgrade -y -V"
Hit:1 http://vwakviie2ienjx6t.onion/debian stretch InRelease
Hit:2 http://sgvtcaew4bxjd7ln.onion stretch/updates InRelease
Hit:3 http://deb.qubes-os.org/r3.2/vm stretch-testing InRelease
Hit:5 http://deb.bitmask.net/debian stretch InRelease
Hit:4 http://archive-3.kali.org/kali kali-rolling InRelease
Reading package lists...
Reading package lists...
Building dependency tree...
Reading state information...
Calculating upgrade...
The following packages have been kept back:
qubes-gui-agent (3.2.8+deb9u1 => 3.2.11-1+deb9u1)
0 upgraded, 0 newly installed, 0 to remove and 1 not upgraded.
[user@dom0 ~]$ qvm-run -p d9-kali "sudo aptitude dist-upgrade"
Reading package lists...
Building dependency tree...
Reading state information...
Reading extended state information...
Initializing package states...
Building tag database...
The following NEW packages will be installed:
xserver-xorg-input-qubes{ab} xserver-xorg-video-dummyqbs{ab}
The following packages will be upgraded:
qubes-gui-agent
1 packages upgraded, 2 newly installed, 0 to remove and 0 not upgraded.
Need to get 66.5 kB of archives. After unpacking 36.9 kB will be used.
The following packages have unmet dependencies:
xserver-xorg-video-dummyqbs : Depends: xorg-video-abi-23 which is a
virtual package, provided by:
- xserver-xorg-core
(2:1.19.0-2), but 2:1.18.4-2 is installed
Depends: xserver-xorg-core (>=
2:1.18.99.901) but 2:1.18.4-2 is installed
xserver-xorg-input-qubes : Depends: xorg-input-abi-24 which is a
virtual package, provided by:
- xserver-xorg-core (2:1.19.0-2),
but 2:1.18.4-2 is installed
Depends: xserver-xorg-core (>=
2:1.18.99.901) but 2:1.18.4-2 is installed
The following actions will resolve these dependencies:
Keep the following packages at their current version:
1) qubes-gui-agent [3.2.8+deb9u1 (now)]
2) xserver-xorg-input-qubes [Not Installed]
3) xserver-xorg-video-dummyqbs [Not Installed]
Accept this solution? [Y/n/q/?]
```
--
qubenix
GPG: B536812904D455B491DCDCDD04BE1E61A3C2E500
--
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 post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/qubes-users/0e8cbae1-d606-6ff4-b65a-79417943bf4b%40riseup.net.
For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Kali VM no longer responding
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Mon, Dec 12, 2016 at 05:10:00PM +, qubenix wrote: > Marek Marczykowski-Górecki: > > Looks like this issue: > > https://github.com/QubesOS/qubes-issues/issues/2514 > > > > Rebuilt package just uploaded to testing repository > > (qubes-gui-agent_3.2.10-2+deb9u1). > > > > > > Doesn't seem to be fixed in stretch, stretch-testing, or > stretch-securitytesting yet. > > ``` > [user@dom0 ~]$ qvm-run -p d9 "sudo apt-get update && sudo apt-get > dist-upgrade -y" > Hit:1 http://vwakviie2ienjx6t.onion/debian stretch InRelease > Hit:2 http://sgvtcaew4bxjd7ln.onion stretch/updates InRelease > Hit:3 http://deb.qubes-os.org/r3.2/vm stretch-testing InRelease > Hit:4 http://deb.qubes-os.org/r3.2/vm stretch-securitytesting InRelease > Reading package lists... > Reading package lists... > Building dependency tree... > Reading state information... > Calculating upgrade... > 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. > [user@dom0 ~]$ qvm-run -p d9 "sudo dpkg -l" | grep qubes-gui > ii qubes-gui-agent 3.2.8+deb9u1 amd64 Makes X11 windows available to > qubes dom0 > ``` Interesting, I have qubes-gui-agent 3.2.11 already, from stretch-testing. Do you have some caching proxy in between? - -- Best Regards, Marek Marczykowski-Górecki Invisible Things Lab A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQEcBAEBCAAGBQJYTxerAAoJENuP0xzK19csdMMH/iJr7fL/7PkzfLmExgc/Q7wi vp4M3UUo4j+gk70ROhR3I2kvLNccgeYmKnR5n2Mw1vTO9/mfGyHoXvZXx3+DPz33 o22MnV/ZBicRpBHFy3FxQ3LnLSmpnRy9xNHzuyWQA1U3ASS4CJtEUIXVaAOSExhv uBZwqgGiBo1h14q4NTSi+wVvhXTxCCnDsv6kf8qUnNDcUo+zrubr+A4wm2qfwH1i DcPNc5j1+FXX/NQMjT9nMdeb9Ri68bcXsapjUtq1FZuZda0Q2rcTaBpEgv4U+pYR zStJWxje+oLxCdCMttByA3gHGjLXNDhqQLNJnSr/YFsaERW7gnLIXMWpuFjk7f4= =Z1cq -END PGP SIGNATURE- -- 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 post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/20161212213330.GH1180%40mail-itl. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Kali VM no longer responding
Marek Marczykowski-Górecki: > On Mon, Dec 12, 2016 at 12:17:16AM +, a.mcwh...@yandex.com wrote: >> That means not only me has the same issue with debian-9 template. I've >> started reinstalling template. > >> On December 12, 2016 11:01:00 AM AEDT, qubenix wrote: >>> Lucas Arnström: Hi, I have been using a debian template converted into kali for quite some time. But recently, neither the kali template nor any appvms >>> based on it are responding. I can start the vms just fine, but cant do much other than that. It seems to be some recent change that induced this problem, considering i have been able to use the very same vms for >>> quite some time. But after my last update they all stopped working. I have attempted to do a complete rebuild of my kali template. I got everything set up, but as soon as I restarted the template I got the same issue again. I'm attaching the logs. // Lucas >>> >>> I've had this same experience after a dist-upgrade on my debian-9 >>> template (d9) about 12 hours ago. I had made a clone of this template >>> about two weeks ago and added the kali repos and some packages. >>> Strangely, my kali template (and AppVM based on it) work normal even >>> though it was also upgraded at the same time. >>> >>> ``` >>> user@dom0:~$ qvm-run -p d9 gnome-terminal >>> Unable to init server: Could not connect: Connection refused >>> Failed to parse arguments: Cannot open display: >>> ``` > > Looks like this issue: > https://github.com/QubesOS/qubes-issues/issues/2514 > > Rebuilt package just uploaded to testing repository > (qubes-gui-agent_3.2.10-2+deb9u1). > > Doesn't seem to be fixed in stretch, stretch-testing, or stretch-securitytesting yet. ``` [user@dom0 ~]$ qvm-run -p d9 "sudo apt-get update && sudo apt-get dist-upgrade -y" Hit:1 http://vwakviie2ienjx6t.onion/debian stretch InRelease Hit:2 http://sgvtcaew4bxjd7ln.onion stretch/updates InRelease Hit:3 http://deb.qubes-os.org/r3.2/vm stretch-testing InRelease Hit:4 http://deb.qubes-os.org/r3.2/vm stretch-securitytesting InRelease Reading package lists... Reading package lists... Building dependency tree... Reading state information... Calculating upgrade... 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. [user@dom0 ~]$ qvm-run -p d9 "sudo dpkg -l" | grep qubes-gui ii qubes-gui-agent 3.2.8+deb9u1 amd64 Makes X11 windows available to qubes dom0 ``` -- qubenix GPG: B536812904D455B491DCDCDD04BE1E61A3C2E500 -- 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 post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/c5b9c017-5864-abb5-529b-b995500ca705%40riseup.net. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Kali VM no longer responding
Marek Marczykowski-Górecki: > On Mon, Dec 12, 2016 at 12:17:16AM +, a.mcwh...@yandex.com wrote: >> That means not only me has the same issue with debian-9 template. I've >> started reinstalling template. > >> On December 12, 2016 11:01:00 AM AEDT, qubenix wrote: >>> Lucas Arnström: Hi, I have been using a debian template converted into kali for quite some time. But recently, neither the kali template nor any appvms >>> based on it are responding. I can start the vms just fine, but cant do much other than that. It seems to be some recent change that induced this problem, considering i have been able to use the very same vms for >>> quite some time. But after my last update they all stopped working. I have attempted to do a complete rebuild of my kali template. I got everything set up, but as soon as I restarted the template I got the same issue again. I'm attaching the logs. // Lucas >>> >>> I've had this same experience after a dist-upgrade on my debian-9 >>> template (d9) about 12 hours ago. I had made a clone of this template >>> about two weeks ago and added the kali repos and some packages. >>> Strangely, my kali template (and AppVM based on it) work normal even >>> though it was also upgraded at the same time. >>> >>> ``` >>> user@dom0:~$ qvm-run -p d9 gnome-terminal >>> Unable to init server: Could not connect: Connection refused >>> Failed to parse arguments: Cannot open display: >>> ``` > > Looks like this issue: > https://github.com/QubesOS/qubes-issues/issues/2514 > > Rebuilt package just uploaded to testing repository > (qubes-gui-agent_3.2.10-2+deb9u1). > > Doesn't seem to be fixed in stretch, stretch-testing, or stretch-securitytesting yet. ``` [user@dom0 ~]$ qvm-run -p d9 "sudo apt-get update && sudo apt-get dist-upgrade -y" Hit:1 http://vwakviie2ienjx6t.onion/debian stretch InRelease Hit:2 http://sgvtcaew4bxjd7ln.onion stretch/updates InRelease Hit:3 http://deb.qubes-os.org/r3.2/vm stretch-testing InRelease Hit:4 http://deb.qubes-os.org/r3.2/vm stretch-securitytesting InRelease Reading package lists... Reading package lists... Building dependency tree... Reading state information... Calculating upgrade... 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. [user@dom0 ~]$ qvm-run -p d9 "sudo dpkg -l" | grep qubes-guiii qubes-gui-agent 3.2.8+deb9u1 amd64Makes X11 windows available to qubes dom0 ``` -- qubenix GPG: B536812904D455B491DCDCDD04BE1E61A3C2E500 -- 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 post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/43f95f6f-3e98-a174-196c-d3799f1f565c%40riseup.net. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Kali VM no longer responding
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Mon, Dec 12, 2016 at 12:17:16AM +, a.mcwh...@yandex.com wrote: > That means not only me has the same issue with debian-9 template. I've > started reinstalling template. > > On December 12, 2016 11:01:00 AM AEDT, qubenix wrote: > >Lucas Arnström: > >> Hi, I have been using a debian template converted into kali for quite > >> some time. But recently, neither the kali template nor any appvms > >based > >> on it are responding. I can start the vms just fine, but cant do much > >> other than that. It seems to be some recent change that induced this > >> problem, considering i have been able to use the very same vms for > >quite > >> some time. But after my last update they all stopped working. > >> > >> I have attempted to do a complete rebuild of my kali template. I got > >> everything set up, but as soon as I restarted the template I got the > >> same issue again. > >> > >> I'm attaching the logs. > >> > >> // Lucas > >> > > > >I've had this same experience after a dist-upgrade on my debian-9 > >template (d9) about 12 hours ago. I had made a clone of this template > >about two weeks ago and added the kali repos and some packages. > >Strangely, my kali template (and AppVM based on it) work normal even > >though it was also upgraded at the same time. > > > >``` > >user@dom0:~$ qvm-run -p d9 gnome-terminal > >Unable to init server: Could not connect: Connection refused > >Failed to parse arguments: Cannot open display: > >``` Looks like this issue: https://github.com/QubesOS/qubes-issues/issues/2514 Rebuilt package just uploaded to testing repository (qubes-gui-agent_3.2.10-2+deb9u1). - -- Best Regards, Marek Marczykowski-Górecki Invisible Things Lab A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQEcBAEBCAAGBQJYThG0AAoJENuP0xzK19csldEH/jrTxcryYPNjC/umInRN2BG4 Lgc3EaAdtlF+wVnW+EKD0aq/8Xiyxq0VetCiGHRMH5ia4o9StnUnFQUTIE77gWuJ ocy7XfP+n8rhpBfE/cCpVVeUZiFTJMP4CgRAmnw5o4od1Qx0Kf6t15ORc92GjXRt aW1MZBkRfWSoXDWHaux8flw2UvNo5tSI3ugyo3eRSRJxCmKDvgBRoSW/OXZPdhUV VHgt2mGouf1UALO/OSSqvewlsD93AEyh8hjio3qjtCziFzTEsHT9N7jzFdpB8R53 LN/XFF9IxjXiIMB/UEVDRe+ypWhg6TNfUku/ZE5TCTLeMBKgj132738bb7UYsZA= =MQId -END PGP SIGNATURE- -- 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 post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/20161212025547.GW16264%40mail-itl. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Kali VM no longer responding
That means not only me has the same issue with debian-9 template. I've started reinstalling template. On December 12, 2016 11:01:00 AM AEDT, qubenix wrote: >Lucas Arnström: >> Hi, I have been using a debian template converted into kali for quite >> some time. But recently, neither the kali template nor any appvms >based >> on it are responding. I can start the vms just fine, but cant do much >> other than that. It seems to be some recent change that induced this >> problem, considering i have been able to use the very same vms for >quite >> some time. But after my last update they all stopped working. >> >> I have attempted to do a complete rebuild of my kali template. I got >> everything set up, but as soon as I restarted the template I got the >> same issue again. >> >> I'm attaching the logs. >> >> // Lucas >> > >I've had this same experience after a dist-upgrade on my debian-9 >template (d9) about 12 hours ago. I had made a clone of this template >about two weeks ago and added the kali repos and some packages. >Strangely, my kali template (and AppVM based on it) work normal even >though it was also upgraded at the same time. > >``` >user@dom0:~$ qvm-run -p d9 gnome-terminal >Unable to init server: Could not connect: Connection refused >Failed to parse arguments: Cannot open display: >``` > >-- >qubenix >GPG: B536812904D455B491DCDCDD04BE1E61A3C2E500 > >-- >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 post to this group, send email to qubes-users@googlegroups.com. >To view this discussion on the web visit >https://groups.google.com/d/msgid/qubes-users/7851f332-b97d-e5cb-3bb6-02d09be245da%40riseup.net. >For more options, visit https://groups.google.com/d/optout. -- 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 post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/11C7A11E-265A-4FDC-BAF0-6224A905D455%40yandex.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Kali VM no longer responding
Lucas Arnström: > Hi, I have been using a debian template converted into kali for quite > some time. But recently, neither the kali template nor any appvms based > on it are responding. I can start the vms just fine, but cant do much > other than that. It seems to be some recent change that induced this > problem, considering i have been able to use the very same vms for quite > some time. But after my last update they all stopped working. > > I have attempted to do a complete rebuild of my kali template. I got > everything set up, but as soon as I restarted the template I got the > same issue again. > > I'm attaching the logs. > > // Lucas > I've had this same experience after a dist-upgrade on my debian-9 template (d9) about 12 hours ago. I had made a clone of this template about two weeks ago and added the kali repos and some packages. Strangely, my kali template (and AppVM based on it) work normal even though it was also upgraded at the same time. ``` user@dom0:~$ qvm-run -p d9 gnome-terminal Unable to init server: Could not connect: Connection refused Failed to parse arguments: Cannot open display: ``` -- qubenix GPG: B536812904D455B491DCDCDD04BE1E61A3C2E500 -- 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 post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/7851f332-b97d-e5cb-3bb6-02d09be245da%40riseup.net. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Kali VM no longer responding
Hi, I have been using a debian template converted into kali for quite some time. But recently, neither the kali template nor any appvms based on it are responding. I can start the vms just fine, but cant do much other than that. It seems to be some recent change that induced this problem, considering i have been able to use the very same vms for quite some time. But after my last update they all stopped working. I have attempted to do a complete rebuild of my kali template. I got everything set up, but as soon as I restarted the template I got the same issue again. I'm attaching the logs. // Lucas -- 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 post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/aa1e0c52-28d3-a4d9-eae9-a0e0a859ecfa%40arnstrom.se. For more options, visit https://groups.google.com/d/optout. [0.00] x86/PAT: Configuration [0-7]: WB WT UC- UC WC WP UC UC [0.00] Initializing cgroup subsys cpuset [0.00] Initializing cgroup subsys cpu [0.00] Initializing cgroup subsys cpuacct [0.00] Linux version 4.4.14-11.pvops.qubes.x86_64 (user@release) (gcc version 5.3.1 20160406 (Red Hat 5.3.1-6) (GCC) ) #1 SMP Tue Jul 19 01:14:58 UTC 2016 [0.00] Command line: root=/dev/mapper/dmroot ro nomodeset console=hvc0 rd_NO_PLYMOUTH rd.plymouth.enable=0 plymouth.enable=0 nopat [0.00] x86/fpu: xstate_offset[2]: 576, xstate_sizes[2]: 256 [0.00] x86/fpu: Supporting XSAVE feature 0x01: 'x87 floating point registers' [0.00] x86/fpu: Supporting XSAVE feature 0x02: 'SSE registers' [0.00] x86/fpu: Supporting XSAVE feature 0x04: 'AVX registers' [0.00] x86/fpu: Enabled xstate features 0x7, context size is 832 bytes, using 'standard' format. [0.00] x86/fpu: Using 'eager' FPU context switches. [0.00] ACPI in unprivileged domain disabled [0.00] Released 0 page(s) [0.00] e820: BIOS-provided physical RAM map: [0.00] Xen: [mem 0x-0x0009] usable [0.00] Xen: [mem 0x000a-0x000f] reserved [0.00] Xen: [mem 0x0010-0xf9ff] usable [0.00] x86/PAT: PAT support disabled. [0.00] NX (Execute Disable) protection: active [0.00] DMI not present or invalid. [0.00] Hypervisor detected: Xen [0.00] e820: last_pfn = 0xfa000 max_arch_pfn = 0x4 [0.00] MTRR: Disabled [0.00] RAMDISK: [mem 0x02055000-0x02b14fff] [0.00] NUMA turned off [0.00] Faking a node at [mem 0x-0xf9ff] [0.00] NODE_DATA(0) allocated [mem 0x18839000-0x1884afff] [0.00] Zone ranges: [0.00] DMA [mem 0x1000-0x00ff] [0.00] DMA32[mem 0x0100-0xf9ff] [0.00] Normal empty [0.00] Movable zone start for each node [0.00] Early memory node ranges [0.00] node 0: [mem 0x1000-0x0009] [0.00] node 0: [mem 0x0010-0xf9ff] [0.00] Initmem setup node 0 [mem 0x1000-0xf9ff] [0.00] p2m virtual area at c900, size is 80 [0.00] Remapped 0 page(s) [0.00] SFI: Simple Firmware Interface v0.81 http://simplefirmware.org [0.00] smpboot: Allowing 4 CPUs, 0 hotplug CPUs [0.00] e820: [mem 0xfa00-0x] available for PCI devices [0.00] Booting paravirtualized kernel on Xen [0.00] Xen version: 4.6.3 (preserve-AD) [0.00] clocksource: refined-jiffies: mask: 0x max_cycles: 0x, max_idle_ns: 1910969940391419 ns [0.00] setup_percpu: NR_CPUS:64 nr_cpumask_bits:64 nr_cpu_ids:4 nr_node_ids:1 [0.00] PERCPU: Embedded 34 pages/cpu @880013e0 s98392 r8192 d32680 u524288 [0.00] PV qspinlock hash table entries: 256 (order: 0, 4096 bytes) [0.00] Built 1 zonelists in Node order, mobility grouping on. Total pages: 1007882 [0.00] Policy zone: DMA32 [0.00] Kernel command line: root=/dev/mapper/dmroot ro nomodeset console=hvc0 rd_NO_PLYMOUTH rd.plymouth.enable=0 plymouth.enable=0 nopat [0.00] PID hash table entries: 4096 (order: 3, 32768 bytes) [0.00] Memory: 298936K/4095612K available (7533K kernel code, 1247K rwdata, 3404K rodata, 1528K init, 1472K bss, 3796676K reserved, 0K cma-reserved) [0.00] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1 [0.00] Hierarchical RCU implementation. [0.00] Build-time adjustment of leaf fanout to 64. [0.000
