Re: [qubes-users] bug ?

[unman]

On Mon, May 17, 2021 at 03:16:10PM +0200, haaber wrote:
> Hello, I followed a link in my mailVM-thunderbird, which configured to
> open links inside a new tempVM. When I reboot the parent mailVM, the
> child-disp-VM dies with it. This is not what I expected.
> 
> Is it some wanted behaviour or a bug? Cheers
> 

It is, I think, wanted, but not by you.
Because the disposableVM was spawned from the parent, it is reaped when
the parent dies.
To keep the disposableVM runninng you would need to create it from dom0
and then "qvm-open" to that disposableVM .

-- 
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/20210517132456.GA30032%40thirdeyesecurity.org.

[qubes-users] bug ?

[haaber]

Hello, I followed a link in my mailVM-thunderbird, which configured to
open links inside a new tempVM. When I reboot the parent mailVM, the
child-disp-VM dies with it. This is not what I expected.

Is it some wanted behaviour or a bug? Cheers

--
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/f831b553-deab-60ee-8b80-ba1d5cd8acca%40web.de.

[qubes-users] bug? after cloning fedora32 qube - gnome terminal stop working

[Eva Star]

Hello,
After cloning fedora32 qube - gnome terminal stop working. 
Is it a bug?

-- 
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/5ca239bb-11d7-4717-9944-91f31f9ee572o%40googlegroups.com.

Re: [qubes-users] Bug Thunderbird: kills addons after last update

[scurge1tl]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512



scurge1tl:
>
>
> scurge1tl:
>> Today's upgrade of Thunderbird to 68.2.2 (64-bit) killed all
>> addons in Whonix-ws-15 AppVMs.
>>
>> Enigmail seems to be already running, but Torbirdy and Qubes
>> addon for Attachments opening in a DispVM disappeared.
>>
>>
>
> Update. Newly created anon-whonix through sudo qubesctl state.sls
> qvm.anon-whonix doesnt include any addons by default on first
> launch. No Torbirdy, Qubes-attachments nor Enigmail.
>
> Manual install is possible only for Enigmail, but Thunderbirds'
> Enigmail somehow cant work with my backend gpg-split. It launches
> work-gpg, asks me for the confirmation, but than cant decrypt or
> even load emails.
>
> But qubes-gpg-client can work with my gpg backend easily, without
> any issue.
>

Is there anything new in this regard?

-BEGIN PGP SIGNATURE-

iQKTBAEBCgB9FiEExlmPb5HoPUTt+CQT44JZDAWK6UwFAl3UCdZfFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEM2
NTk4RjZGOTFFODNENDRFREY4MjQxM0UzODI1OTBDMDU4QUU5NEMACgkQ44JZDAWK
6UyyRg//ZC9LLtFZsFdFQ31lcJk/576fvaVsaca5goQtk1DeTTfYb5I9l4avFZTS
xVZJZV1d29X18vPyf0rjXuzoISMR7sjq7VMN0VEWE8yG4qNdbDKMevo3mXtItpEX
M7xol7aW3dJMRtGfvci3CeVCiqVjjJXZ4wWHFSX6JdBgY/QgA7F+pdhdSeCcEMQZ
F5jx3s5YXvTXd5+0dhb78Im4DSugAT4udjjkhcYxdnI8nJnNbrxJEVh39UbLAi9X
U21mKj4RkpYoCBrzeFWcpeF2RNWk2acq8sEtjbb7HBk8RE69K/0N1Zr7Yf3SZHY8
NWzcgsxz8kkRa7cwmGkMp9NdKI/RigotH4zHMNiFgg4shLW2VplufhcdEhem4lCo
xmDcjBZlLAtutR1betrHQl790QNv8jZJKXwXden436/I2IFE0JVU+tiwkcCHE6Jy
CyynFlZrDqmBdU4512/L1yNyuAajSgjSTuybszAjZCV1QOLSwaZlaHeZy+x78tE1
VYwWUPVUGg8J7TSc6nKzt1lnv/b6dAFFrXpazWtJZnQiJ/HiBn3dGJEXXqtlYaAL
VLyn0mrJLfY6y7Z+VwOprztJ5CNgKu+Khg4KeEFGL34K/i/o+OC85OvrSxWFqSS/
YQprW7T6GlCu4EBaACF2CHptbYQqSAUSOTsO1vnhBBMrSlIOP3c=
=uMgo
-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 view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/1ae50d81-ba97-b0c8-ea22-3b5054b436f8%40cock.li.


0xC1F4E83AF470A4ED.asc
Description: application/pgp-keys

Re: [qubes-users] Bug Thunderbird: kills addons after last update

[scurge1tl]

scurge1tl:
> Today's upgrade of Thunderbird to 68.2.2 (64-bit) killed all addons in
> Whonix-ws-15 AppVMs.
> 
> Enigmail seems to be already running, but Torbirdy and Qubes addon
> for Attachments opening in a DispVM disappeared.
> 
>

Update. Newly created anon-whonix through sudo qubesctl state.sls
qvm.anon-whonix doesnt include any addons by default on first launch. No
Torbirdy, Qubes-attachments nor Enigmail.

Manual install is possible only for Enigmail, but Thunderbirds' Enigmail
somehow cant work with my backend gpg-split. It launches work-gpg, asks
me for the confirmation, but than cant decrypt or even load emails.

But qubes-gpg-client can work with my gpg backend easily, without any issue.

-- 
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/e74e6a04-6ce8-be06-cc59-f0578909b7a5%40cock.li.


0xC1F4E83AF470A4ED.asc
Description: application/pgp-keys

[qubes-users] Bug Thunderbird: kills addons after last update

[scurge1tl]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Today's upgrade of Thunderbird to 68.2.2 (64-bit) killed all addons in
Whonix-ws-15 AppVMs.

Enigmail seems to be already running, but Torbirdy and Qubes addon
for Attachments opening in a DispVM disappeared.

-BEGIN PGP SIGNATURE-

iQKTBAEBCgB9FiEExlmPb5HoPUTt+CQT44JZDAWK6UwFAl3SfWFfFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEM2
NTk4RjZGOTFFODNENDRFREY4MjQxM0UzODI1OTBDMDU4QUU5NEMACgkQ44JZDAWK
6UyKXg//Q6qKn34KAE0iUjRuTgY76YQBmLcSXZqTSjVJtNqOd7Uxg/siJLpyEUSK
sFtc1XWJzjEMKKr4fZVKp/Czl631xs92ouKg/mewfUdiWvBwZb6fegp6kOEr+x1m
+BPy7jXkfXOs+uobxx7lgIskzysU9AbaryZDkwyCS0aCgfAH8sxBgNtuff1xU9Cq
lzU/2hrvcU0EbFPpgCkstWqZODa+e29GgWUx7T38/OUlFGtjV5y+ZdrHl+pdC9wN
N9WPhPwlneZYOSETVU0bamYo3kzodyrJzTcCtwuPGzx9xxLYa4HPUQg9v05rXfzN
lxSEgMlFXsXlUazjXUyl7dSqkyEKfSUXa21ocuzIbLddviEu2nEEGI2iMwIqgoEF
Gok6HSjBNraCbZWGP2tKFAvVi6dkgDBcCb5Q2GRCkKoth6hpclBGxtHVv8knMN7J
3yqL9j5JJZzrm2CMx6XYPf3cUcGGnt/KLEIXWIWVfAZRTWCJ4HdaFyf8VPXwYkpT
9Ll3J2ymUK9HtS3jmaLF5A25yP7IXMEViIqUozTFlxA1qhKALixX8Tj+XQfafGHN
pw3yrNmrUTgWoHvgPX7JlStQG9V0eFnup79LU6aHBtDpcyzsO3fbL8TVTnZIVePR
nyXujb0JpVgPphY19/iOgrmwsZJY9wehOhhkgeS7iMK1p4NWof4=
=4ms1
-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 view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/d4d258a0-429c-cf64-b0fb-b21539346947%40cock.li.


0xC1F4E83AF470A4ED.asc
Description: application/pgp-keys

Re: [qubes-users] [bug] Backup restore: Modal success dialog should not use "Warning" icon

[AJ Jordan]

On Thu, May 23, 2019 at 05:07:00AM +, g80vmgm...@riseup.net wrote:

> When restoring from backup, successful completion results in a modal
> dialog labeled, "Finished successfully!".  This dialog uses an
> exclamation point-style "Warning" icon.  This icon gives the user the
> wrong impression.  Instead, the icon should be a green checkmark or
> something similarly recognizable as an indicator of success.

I would suggest filing a bug in the issue tracker[1], where it is much
more likely to be noticed by the developers. More broadly the Qubes UI
is full of icon problems of this nature; see for example issue
#4922[2] which is *exactly* the same problem as the one you've
noticed.

 [1]: https://github.com/QubesOS/qubes-issues/issues
 [2]: https://github.com/QubesOS/qubes-issues/issues/4922

-- 
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/20190525000301.ofqxirvq46f6lsvq%40failover.strugee.net.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] [bug] Backup restore: Modal success dialog should not use "Warning" icon

[g80vmgmsqw]

When restoring from backup, successful completion results in a modal
dialog labeled, "Finished successfully!".  This dialog uses an
exclamation point-style "Warning" icon.  This icon gives the user the
wrong impression.  Instead, the icon should be a green checkmark or
something similarly recognizable as an indicator of success.

-- 
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/c920baf2-5135-9ff7-2d3b-b2558bb59407%40riseup.net.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] [Bug?] whonix-ws clock out of synch after suspend (R4.0)

[[799]]

Hello,

On 05/15 10:57, Dimitri wrote:
> Hi,
> I noticed that the clock in whonix-ws based VMs is not synchronized after 
> sleep mode. If I have my computer in sleep mode for 2h then the VMs clock is 
> 2h in the past.
> To me this looks like a bug. 
> Large clock skews can potentially harm anonymity.

I have the same problem.

I have set the time manually using the following command in sys-whonix and my 
anon-whonix AppVM:

   user@host:~$ sudo date +%T -s "22:18:00"


which sets the time to my current local time (germany).

Strangely I still get an error message when running whonixcheck.
Why is there a message "NTP synchronized: no" ?

Shouldn't the time always be synchronized as we're running virtual machines?


user@host:~$ whonixcheck
[INFO] [whonixcheck] sys-whonix | Whonix-Gateway | whonix-gw Template-Based 
ProxyVM | Tue May 15 22:29:23 UTC 2018
dmesg: read kernel buffer failed: Operation not permitted
[INFO] [whonixcheck] Connected to Tor.
[ERROR] [whonixcheck] Systemd Clock Check Result:
Unexpected results by timedatectl.
timedatectl_output_pretty:
  Local time: Tue 2018-05-15 22:29:25 UTC
  Universal time: Tue 2018-05-15 22:29:25 UTC
RTC time: n/a
   Time zone: Etc/UTC (UTC, +)
 NTP enabled: yes
NTP synchronized: no
 RTC in local TZ: no
  DST active: n/a
It is generally recommended to keep the default as per Whonix Design. [1]
If you did not change timezone related settings, please report this Whonix bug.
If you know what you are doing and changed this on purpose, feel free to
disable this check. [2]

[1] https://www.whonix.org/wiki/Dev/Design-Shared#timezone
[2] Create a file /etc/whonix.d/50_whonixcheck_user and add:
whonixcheck_skip_functions+=" check_systemd_clock "


[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+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/20180515203810.tpgltwx3v5sqemhk%40my-privmail.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] [Bug?] whonix-ws clock out of synch after suspend (R4.0)

[awokd]

On Tue, May 15, 2018 8:47 pm, 799 wrote:
> Hello,
>
> On 05/15 10:57, Dimitri wrote:
>> Hi,
>> I noticed that the clock in whonix-ws based VMs is not synchronized
>> after
> sleep mode. If I have my computer in sleep mode for 2h then the VMs clock
> is 2h in the past.
>> To me this looks like a bug.
>> Large clock skews can potentially harm anonymity.
>
> I have the same problem.
>
> I have set the time manually using the following command in sys-whonix and
> my anon-whonix AppVM:
>
>user@host:~$ sudo date +%T -s "22:18:00"
>
>
> which sets the time to my current local time (germany).
>
> Strangely I still get an error message when running whonixcheck.
> Why is there a message "NTP synchronized: no" ?
>
> Shouldn't the time always be synchronized as we're running virtual
> machines?

I think this may have been addressed in Whonix 14. On Whonix 13 on R3.2
with DispVMs, I worked around the issue by disabling sdwdate
(https://phabricator.whonix.org/T695). I'm not sure that's the safest
approach or if it will help on a normal suspend. So try Whonix 14 first,
then disabling sdwdate if it still isn't working.

NTP is disabled in Whonix templates. https://www.whonix.org/wiki/Time_Attacks


-- 
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/166a8e7971fb9fb83088d19853723c22%40elude.in.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] [Bug?] whonix-ws clock out of synch after suspend (R4.0)

[799]

Hello,

On 05/15 10:57, Dimitri wrote:
> Hi,
> I noticed that the clock in whonix-ws based VMs is not synchronized after
sleep mode. If I have my computer in sleep mode for 2h then the VMs clock
is 2h in the past.
> To me this looks like a bug.
> Large clock skews can potentially harm anonymity.

I have the same problem.

I have set the time manually using the following command in sys-whonix and
my anon-whonix AppVM:

   user@host:~$ sudo date +%T -s "22:18:00"


which sets the time to my current local time (germany).

Strangely I still get an error message when running whonixcheck.
Why is there a message "NTP synchronized: no" ?

Shouldn't the time always be synchronized as we're running virtual machines?


user@host:~$ whonixcheck
[INFO] [whonixcheck] sys-whonix | Whonix-Gateway | whonix-gw Template-Based
ProxyVM | Tue May 15 22:29:23 UTC 2018
dmesg: read kernel buffer failed: Operation not permitted
[INFO] [whonixcheck] Connected to Tor.
[ERROR] [whonixcheck] Systemd Clock Check Result:
Unexpected results by timedatectl.
timedatectl_output_pretty:
  Local time: Tue 2018-05-15 22:29:25 UTC
  Universal time: Tue 2018-05-15 22:29:25 UTC
RTC time: n/a
   Time zone: Etc/UTC (UTC, +)
 NTP enabled: yes
NTP synchronized: no
 RTC in local TZ: no
  DST active: n/a
It is generally recommended to keep the default as per Whonix Design. [1]
If you did not change timezone related settings, please report this Whonix
bug.
If you know what you are doing and changed this on purpose, feel free to
disable this check. [2]

[1] https://www.whonix.org/wiki/Dev/Design-Shared#timezone
[2] Create a file /etc/whonix.d/50_whonixcheck_user and add:
whonixcheck_skip_functions+=" check_systemd_clock "


[799]



On 15 May 2018 at 19:57, Dimitri  wrote:

> Hi,
> I noticed that the clock in whonix-ws based VMs is not synchronized after
> sleep mode. If I have my computer in sleep mode for 2h then the VMs clock
> is 2h in the past.
>
> To me this looks like a bug.
>
> Large clock skews can potentially harm anonymity.
>
> --
> 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/1a102f3c-da72-4987-b688-edde6f9ebe75%40googlegroups.com.
> 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/CAJ3yz2vQb0ywD_V3HsvYppG6-c-jxL6pQLfZULmBxQgN0Zz3Lw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] [Bug?] whonix-ws clock out of synch after suspend (R4.0)

[Dimitri]

Hi,
I noticed that the clock in whonix-ws based VMs is not synchronized after sleep 
mode. If I have my computer in sleep mode for 2h then the VMs clock is 2h in 
the past.

To me this looks like a bug.

Large clock skews can potentially harm anonymity.

-- 
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/1a102f3c-da72-4987-b688-edde6f9ebe75%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] [Bug] Windows closing immediately after opening them in jetbrains java based ide in Qubes 4

[carre89]

I am encountering a bug where the pop up window closes immediately after I open 
it in jetbrain's pycharm. It does this when I try the 
auto-correction(alt-enter). Is anyone else encountering this? 

This is happening in a fresh install of the latest version of Qube OS (4.0 - 
5/4/18). 

-- 
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/8e7ced12-442f-4b8d-8a9d-132978b97267%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Bug in qubes-input-sender

['awokd' via qubes-users]

On Thu, April 5, 2018 9:38 pm, Andrzej Andrzej wrote:
> any idea?

Sorry, not specifically but you might want to search
https://github.com/QubesOS/qubes-issues/issues for similar ones and/or
open a new one if you don't see any.

-- 
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/4047067ebd3a1c410b1ec036e6a5c5ea.squirrel%40tt3j2x4k5ycaa5zt.onion.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Bug in qubes-input-sender

[Andrzej Andrzej]

any idea?

-- 
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/396506439.19764.1522964320990%40ichabod.co-bxl.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Bug (R4.0): VM fail to start after hard power off

[Chris Laprise]

On 04/02/2018 05:42 AM, Dimitri wrote:

Hi,
I realized that some VMs refuse to start after a hard power-off (hold power 
button for 10s). When running 'qvm-start test' I get 'vm-test-private missing'. 
But this thin volume is actually there. Also the volume 'vm-test-private-snap' 
is still present. Does the snapshot not get written back to the private image?

This case needs to be handled somehow.

As long as this is not fixed: How can I manually fix it?

Thanks for help!



Try this in dom0:

sudo pvscan --cache --activate ay
sudo systemctl restart qubesd
qvm-start test

--

Chris Laprise, tas...@posteo.net
https://github.com/tasket
https://twitter.com/ttaskett
PGP: BEE2 20C5 356E 764A 73EB  4AB3 1DC4 D106 F07F 1886

--
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/35f8c0f6-e8f7-8f18-ce17-30dc17a18395%40posteo.net.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Bug (R4.0): VM fail to start after hard power off

[Dimitri]

Hi,
I realized that some VMs refuse to start after a hard power-off (hold power 
button for 10s). When running 'qvm-start test' I get 'vm-test-private missing'. 
But this thin volume is actually there. Also the volume 'vm-test-private-snap' 
is still present. Does the snapshot not get written back to the private image?

This case needs to be handled somehow.

As long as this is not fixed: How can I manually fix it?

Thanks for help!

-- 
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/30f01c67-cb86-4e60-b10c-9bcde5c6b07f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Bug in qubes-input-sender

[Andrzej Andrzej]

The problem is that after connecting the mouse to the computer, the mouse can 
run for 10 minutes, then the system disconnects it from sys-usb, and then 
connects it again without any user interaction.
The second problem is that after connecting the keyboard via usb to sys-usb the 
keyboard does not work, only the backlight of the keyboard works, but the 
keyboard itself does not work. No buttons were detected in the system, 
therefore you can not write on it.

Logs from sys-usb
https://0bin.net/paste/B+3I3fbBsrNCHzFu#a97f-dAtLaVPeUlyqHNGW9a/0PqUKusDHTqEWrRJE2z

-- 
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/2028224823.118183.1522524881695%40ichabod.co-bxl.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] bug: qubes vm-manager qubes 3.2 current: Unable to rename VM to "ReactOS-Reference"

[ludwig jaffe]

bug: qubes vm-manager qubes 3.2 current: Unable to rename VM to 
"ReactOS-Reference"

Problem:
I installed reactos into a new standalone template vm and thought I could 
derive user vms as in linux based. But this did not work, maybe I dont know 
howto do.
So as a work-around I wanted to make a reference reactos and clone it for 
different tasks.
So renaming it to "ReactOS-Reference" failed!
The /var/lib/qubes/vm-templates/ReactOS-Reference folder
got renamed properly but the Qube VM Manager did not find the VM 
and threw an error.
"Errno 2 No such file or directory"
"
fill_apps_list line no.:71
...appmenu_select.py"
and some more.


To get it running again one had to rename the directory 
var/lib/qubes/vm-templates/ReactOS-Reference to the original name displayed in 
Qubes VM Manager.

So the directory listing should be enhanced to parse more complicated directory 
names, or renaming should be masked in order not to allow "illegal" directory 
names.

Cheers,

Ludwig

-- 
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/f3d25028-5403-43cf-9001-3816b8e6f7ad%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Bug in qubes-backup or tar?

[Rusty Bird]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

svenssona...@gmail.com:
> Emergency recovery of backups as described in
> https://www.qubes-os.org/doc/backup-emergency-restore-v3/ states
> that tar should be able to unpack a qubes backup file.
> 
> [...]
> tar tvf bu/qubes-*
> # Shows only backup-header, size 94 bytes, no other file.
> # Extracting the tar file produces only backup-header.
> # However, the tar file has size 563200 bytes.

The -i (--ignore-zeros) parameter is missing in the tar command.

Rusty
-BEGIN PGP SIGNATURE-

iQJ8BAEBCgBmBQJZRQv0XxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQ4NEI1OUJDRkM2MkIxMjlGRTFCMDZEMDQ0
NjlENzhGNDdBQUYyQURGAAoJEEadePR6ryrfohgQAIra88HMA5feWJTII1Aodg53
yvNYaFHo8YR9RX3GlprYgMDjil8PMy0sHUNWYzN7rAkyqsuyJWzCEI0eeVKOVlK+
nvMbFCAg6259kXnpCcQwYbLvpoLR/IVAntAwMcEEXGPsREQhUoxu1U1Ou/hmgpJN
xg4kUK/+mYebWvNfMBTYDgL+iqv9RMJBhXIctybsb/o0xBq2AmAciZEPZgPBgnBI
9CZDvJA1Zs5tTvW8WShir+JtLMRlOkuACVOJNy6pRzJVkuo3KkaG24GBx5qPXXHb
7NlbuLba7vZI3eF0ApJ20p2gM97ljVJEjBZ75xmbkpPCE9If3LrefEQ7heC0oihJ
m9Y7Z26FN/wDFP2uEop5GLPcINqxr8WaChHLjosDJl+sGonAorrN3aXB5YpMxu9L
RlUgXKb2d24RqET8QghG8q0JYhkwkJYy+HdA67CgrYLYNEMUiC72ZMQCg8bqJQis
1NzDWgmXbf9lBQH8IjLMGcGzGZKBDLyGF4u0ONYoQc8PMURit3K2zwhWFbdlpGa7
/h5q9qfiA2oA2N6ehZsHQ8waCbBGb5KrZEiEs9PPmvZ1zMCg0sIpKRdiYzHsP4B/
sdXW7n7SVaX31AXljOfIxWChpUP3GA0BMZugiZHaKrWwqqqZ0FSR5I8+xROveIHJ
9nt/w5KheaDFIpSYOUo2
=2C80
-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/20170617110109.GA32654%40mutt.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Bug in qubes-backup or tar?

[Connor Page]

qvm-backup has a different syntax and vms are excluded from rather than 
included in a backup.

-- 
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/90133a68-60e2-404a-b3f2-3f6d14415779%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Bug in qubes-backup or tar?

[svenssonaxel]

Emergency recovery of backups as described in 
https://www.qubes-os.org/doc/backup-emergency-restore-v3/ states that tar 
should be able to unpack a qubes backup file.

It seems that qvm-backup produces a corrupt tar file, or the included tar has a 
bug. It seems to include data, but only one file will show up in list or 
extract.

My system is a recently updated 3.2.

# To reproduce, run in dom0:
qvm-create -t fedora-23 -l red test-bu
qvm-start test-bu
qvm-run test-bu 'echo "This text should be included in backup." > examplefile'
qvm-run -p test-bu 'ls -l e*; cat examplefile'
# Shows file and text
qvm-run test-bu 'sudo shutdown 0'
mkdir bu
qvm-backup bu test-bu
# Choose 'y', empty passphrase
tar tvf bu/qubes-*
# Shows only backup-header, size 94 bytes, no other file.
# Extracting the tar file produces only backup-header.
# However, the tar file has size 563200 bytes.

-- 
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/9ba80c06-e1b1-4ba4-b222-e65cb9479211%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Bug with copy and paste to different window

[Jean-Philippe Ouellet]

On Fri, Apr 21, 2017 at 5:22 AM, evo  wrote:
> I have a problem with an appVM based on Fedora24.
> I open LibreOffice and Scribus, then i want to copy and paste from
> office. But if i copy it from office and go to the scribus-window the
> window is not activated... it just still acts with the office-window
> behind the scribus-window... just so, if the scribus-window does not exist.
>
> Is it a bug or something else??

https://github.com/QubesOS/qubes-issues/issues/1455 ?

-- 
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/CABQWM_BcxZXZq4BhYGpwep8d_J4h_RVSDqkjXhxXSAoxNXNQLw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Bug with copy and paste to different window

[evo]

Hello!

I have a problem with an appVM based on Fedora24.
I open LibreOffice and Scribus, then i want to copy and paste from
office. But if i copy it from office and go to the scribus-window the
window is not activated... it just still acts with the office-window
behind the scribus-window... just so, if the scribus-window does not exist.

Is it a bug or something else??

-- 
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/ac93b674-1f33-ee35-523b-229c41fc1490%40aliaks.de.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Bug: Qubes installer will not continue beyond probing install media

[emergencymexican]

I believe I have solved this issue, but it was a frustrating experience for me. 
I tried several USB drives, different OS installs (which worked just fine), and 
removal of the hardware in the expansion slots to try and figure out the issue. 
Turns out it was very simple, and I just had to be there during the very long 
boot process. 

Issue: Qubes installer will act as normal, except for the test media boot 
option, and let you proceed beyond the language and keyboard selection screen. 
When you get to the install screen where you select the additional TemplateVM 
you want, the timezone, and the installation destination, the installer will 
say "Probing install media" and will stay stuck on this screen. The mouse is 
still moveable, and one can click the quit button with action taking place but 
no matter how long the machine is left on this screen, it will not allow the 
installation process to continue. There are no warnings or messages indicating 
that there is any issue.

(my) cause: One HDD had a S.M.A.R.T. event(drive is starting to fail), 
unbeknownst to me, and the removal of this drive fixed the issue and allowed 
the installation process to complete.

-- 
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/00243006-7e29-4071-b070-79b72efa586f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] [bug, 3.2, qubes manager] sys-whonix restart

[Andrew David Wong]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

On 2017-04-02 13:45, Eva Star wrote:
> Trying to restart running sys-whonix constantly give us this
> assert: https://i.imgur.com/YU8sv3H.png
> 

Known issue:

https://github.com/QubesOS/qubes-issues/issues/2438

- -- 
Andrew David Wong (Axon)
Community Manager, Qubes OS
https://www.qubes-os.org
-BEGIN PGP SIGNATURE-

iQIcBAEBCgAGBQJY4c5aAAoJENtN07w5UDAwv/MP/2QjoiW9rKpJLyrfib7B5/6q
2J8WPLamLlR0CgX3JSIMOkxCeAyOPOnyuX2Fj1WcQidiClQYjHdDF1S+Bi2ifyVN
YM5czh2Pfn0h0k1UzLY29XMjpQbsmbsNpxvSFp92kvI6G8b5ZmqqlQ5CFKFsFxPf
TjXyGji7f1fR8b8U/8e+p+/4VukgPD/P2DuBT+oN9nqHLxD+aYrj3SB6PXcRW/qV
CO4M9MxJF4drBGklbCamV2WXzDt6nZItILIHpBZKjoHbWK8PCAPUPiB+ZC1ynA3X
/2ZVufpZhfZXHiThJiExfBlmcJUOtvJUJNurwY5brOYrRkLSvthqF7fhUuZstiqD
1A9XoEY1IVcj3ksRhOrfMPDXrNPDBmrULVtAmk2OMeZ3ujODHvFFZZHC7qxizTa0
g7Wbb4qe/JrSKPnbqWxuf1snQjHm6MyJTICpXyrl8/HXEJXj+svFCfBQNKL6kB0O
L74RlENEGsE4Iwvm9MnIzGxMltQDgf2xtEi0NUjcRjhaPgIXx+Eh1fPRDkRALSYS
fFU+RgiSeUEHpWaQS09HZhDlX1vJSQCUT0YIJYyJF1H+qog1yYbnUmRz8hp7A4o5
o1rcCqXnVyB16upL87ckt0DVJRfPhiQKIHPHdkmjuo+Ua5USx0FQS3aspWbMUmza
Y+/qXewqCY9dlSklJpoZ
=q+33
-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/6d740b0d-89aa-d379-dd67-296776afddfa%40qubes-os.org.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] [bug, 3.2, qubes manager] sys-whonix restart

[Eva Star]

Trying to restart running sys-whonix constantly give us this assert:
https://i.imgur.com/YU8sv3H.png

--
Regards

--
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/686f404c-55a6-bac1-c959-21c182869fc5%40openmailbox.org.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] [bug] qubes-guid crashes when putting debian-9 VM in true XFCE fullscreen

[Andrew]

Hi,

Sorry for the verbose title.  If I put a debian-9 VM in true fullscreen
in XFCE, I get a short hang, then the window disappears.  The VM then
goes 'yellow', and while I can xl console into the VM, I lose all windows.

The GUID log has:
ErrorHandler: BadAccess (attempt to access private resource denied)
 Major opcode: 130 (MIT-SHM)
 Minor opcode: 1 (X_ShmAttach)
 ResourceID:   0x440003c
 Failed serial number:  548
 Current serial number: 549

And indeed, using 'ps' in Dom0 shows that the corresponding qubes-guid
has crashed :(.

The VM dmesg logs are also filled with a bunch of messages like the
following:
[   15.385864] U2MFN_GET_MFN_FOR_PAGE: get_user_pages failed,
ret=0xfff2

I suspect this is related to my most recent qubes-guid update, as this
behavior never occurred before.

Andrew

-- 
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/ef42c32b-0922-952a-df9d-7de7d15541cb%40riseup.net.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Bug - Qubes fails to boot if a USB Audio device is connected to the PC

[raahelps]

On Sunday, January 8, 2017 at 12:14:17 PM UTC-5, Grzesiek Chodzicki wrote:
> W dniu niedziela, 8 stycznia 2017 18:03:47 UTC+1 użytkownik Andrew David Wong 
> napisał:
> > -BEGIN PGP SIGNED MESSAGE-
> > Hash: SHA512
> > 
> > On 2017-01-08 08:30, Grzesiek Chodzicki wrote:
> > > I know that this sounds rather bizarre, but my Qubes instance
> > > consistently gets stuck after GRUB menu if a USB Audio device is
> > > connected to the computer. So far I have a 3/3 repro rate on that.
> > > What type of logs/information should I gather from my machine in
> > > order to troubleshoot that? XL dmesg does print a RMRR warning
> > > about USB controllers
> > > 
> > > Qubes 3.2 Kernel 4.8.12-12 I use a sys-usb AppVM with all
> > > controllers hidden from Dom0.
> > > 
> > 
> > Is your sys-usb set to autostart? If so, try disabling that to see
> > whether the system can boot.
> > 
> > - -- 
> > Andrew David Wong (Axon)
> > Community Manager, Qubes OS
> > https://www.qubes-os.org
> > -BEGIN PGP SIGNATURE-
> > 
> > iQIcBAEBCgAGBQJYcnDpAAoJENtN07w5UDAw8NcP/iQTveiRfsgdJbeweJC84k6V
> > d3UdLc8i7OrFuh4Cya0opcH341OKvCid4Rv3jIVAhRhE+TSVgobKQkXXEEE9UO8u
> > 8l2ugFuUg3gYUv//WIJUmCNZXRXTTT7Tk7JFjXXhyKUjrkD1B9oAhlVPcK3UaUiQ
> > 2lkAgMWVPDpo9mJMoc4GaQlWZX9sDwJ14M75lMa0lPtbN93nmFOOiye6FNIQ20bH
> > pmbuu6bfyI1w53bVMA84HZIXs1msvXfLLO2CaVksntEk8TaiO/MBM8wmXYA9IQrF
> > I3yxsAVm6pjqlkAIABTkGzM6wOrUeHQjgqTewvmQYO+ch5K00r/Jy2/zZwmNYOOx
> > p/qHn0q82GcITe73xDTD2vp6QILkqV3VCeFBPc9JzqrFYYRONtPr3vDyD48EJ2Nb
> > ButtRJXAxqe6QIkfWs614tfZYWzHMgOVSHokiGnoHMIG5OfU8jDD+ywwzLGyt+2Y
> > QZsAL7dKVxxfEybAFIacumC0HyAIJWtbZDcfl6mnP3qmrGbIo8PebzwpOGCkDMFu
> > NS4aC+dmqJQSqfl2yufNYbr+2eZGoPmhE206qfIL0KBM3Cch8M2RytEXHjyBCH4s
> > u5SGaOALrvlM5zWADoTWyhd6PEg9EWEHkl9vo2MkFYq90o7/VIzWQBX15H5uCsYJ
> > wIyI9Itq6I/JD32gR2i0
> > =lqgz
> > -END PGP SIGNATURE-
> 
> Hello Andrew,
> 
> The issue still occurs after disabling autostart of the sys-usb AppVM.

Did you make sure you followed these directions?  
https://www.qubes-os.org/doc/external-audio/

what type of bios boot are you using?  Try legacy boot.How much ram does 
your system have?  

What if you just remove the sys-usb and try booting qubes without it while 
device is attached?

Did you create it manually?  After removing the sys-usb vm then rebooting and 
seeing if qubes boots with the usb attached. Then recreate sys-usb using qubes 
commands
qubesctl top.enable qvm.sys-usb  
qubesctl state.highstate
and repeat audio device instructions.

Try disabling vt-d to identify the bios iommu as possibly the problem.  
Doublecheck bios options.

-- 
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/f8d244fe-8900-4b55-a379-b5e083dd043b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Bug - Qubes fails to boot if a USB Audio device is connected to the PC

[Grzesiek Chodzicki]

W dniu niedziela, 8 stycznia 2017 18:03:47 UTC+1 użytkownik Andrew David Wong 
napisał:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
> 
> On 2017-01-08 08:30, Grzesiek Chodzicki wrote:
> > I know that this sounds rather bizarre, but my Qubes instance
> > consistently gets stuck after GRUB menu if a USB Audio device is
> > connected to the computer. So far I have a 3/3 repro rate on that.
> > What type of logs/information should I gather from my machine in
> > order to troubleshoot that? XL dmesg does print a RMRR warning
> > about USB controllers
> > 
> > Qubes 3.2 Kernel 4.8.12-12 I use a sys-usb AppVM with all
> > controllers hidden from Dom0.
> > 
> 
> Is your sys-usb set to autostart? If so, try disabling that to see
> whether the system can boot.
> 
> - -- 
> Andrew David Wong (Axon)
> Community Manager, Qubes OS
> https://www.qubes-os.org
> -BEGIN PGP SIGNATURE-
> 
> iQIcBAEBCgAGBQJYcnDpAAoJENtN07w5UDAw8NcP/iQTveiRfsgdJbeweJC84k6V
> d3UdLc8i7OrFuh4Cya0opcH341OKvCid4Rv3jIVAhRhE+TSVgobKQkXXEEE9UO8u
> 8l2ugFuUg3gYUv//WIJUmCNZXRXTTT7Tk7JFjXXhyKUjrkD1B9oAhlVPcK3UaUiQ
> 2lkAgMWVPDpo9mJMoc4GaQlWZX9sDwJ14M75lMa0lPtbN93nmFOOiye6FNIQ20bH
> pmbuu6bfyI1w53bVMA84HZIXs1msvXfLLO2CaVksntEk8TaiO/MBM8wmXYA9IQrF
> I3yxsAVm6pjqlkAIABTkGzM6wOrUeHQjgqTewvmQYO+ch5K00r/Jy2/zZwmNYOOx
> p/qHn0q82GcITe73xDTD2vp6QILkqV3VCeFBPc9JzqrFYYRONtPr3vDyD48EJ2Nb
> ButtRJXAxqe6QIkfWs614tfZYWzHMgOVSHokiGnoHMIG5OfU8jDD+ywwzLGyt+2Y
> QZsAL7dKVxxfEybAFIacumC0HyAIJWtbZDcfl6mnP3qmrGbIo8PebzwpOGCkDMFu
> NS4aC+dmqJQSqfl2yufNYbr+2eZGoPmhE206qfIL0KBM3Cch8M2RytEXHjyBCH4s
> u5SGaOALrvlM5zWADoTWyhd6PEg9EWEHkl9vo2MkFYq90o7/VIzWQBX15H5uCsYJ
> wIyI9Itq6I/JD32gR2i0
> =lqgz
> -END PGP SIGNATURE-

Hello Andrew,

The issue still occurs after disabling autostart of the sys-usb AppVM.

-- 
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/3d889653-b6e9-4c0b-854d-4dae694fb76d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Bug - Qubes fails to boot if a USB Audio device is connected to the PC

[Andrew David Wong]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

On 2017-01-08 08:30, Grzesiek Chodzicki wrote:
> I know that this sounds rather bizarre, but my Qubes instance
> consistently gets stuck after GRUB menu if a USB Audio device is
> connected to the computer. So far I have a 3/3 repro rate on that.
> What type of logs/information should I gather from my machine in
> order to troubleshoot that? XL dmesg does print a RMRR warning
> about USB controllers
> 
> Qubes 3.2 Kernel 4.8.12-12 I use a sys-usb AppVM with all
> controllers hidden from Dom0.
> 

Is your sys-usb set to autostart? If so, try disabling that to see
whether the system can boot.

- -- 
Andrew David Wong (Axon)
Community Manager, Qubes OS
https://www.qubes-os.org
-BEGIN PGP SIGNATURE-

iQIcBAEBCgAGBQJYcnDpAAoJENtN07w5UDAw8NcP/iQTveiRfsgdJbeweJC84k6V
d3UdLc8i7OrFuh4Cya0opcH341OKvCid4Rv3jIVAhRhE+TSVgobKQkXXEEE9UO8u
8l2ugFuUg3gYUv//WIJUmCNZXRXTTT7Tk7JFjXXhyKUjrkD1B9oAhlVPcK3UaUiQ
2lkAgMWVPDpo9mJMoc4GaQlWZX9sDwJ14M75lMa0lPtbN93nmFOOiye6FNIQ20bH
pmbuu6bfyI1w53bVMA84HZIXs1msvXfLLO2CaVksntEk8TaiO/MBM8wmXYA9IQrF
I3yxsAVm6pjqlkAIABTkGzM6wOrUeHQjgqTewvmQYO+ch5K00r/Jy2/zZwmNYOOx
p/qHn0q82GcITe73xDTD2vp6QILkqV3VCeFBPc9JzqrFYYRONtPr3vDyD48EJ2Nb
ButtRJXAxqe6QIkfWs614tfZYWzHMgOVSHokiGnoHMIG5OfU8jDD+ywwzLGyt+2Y
QZsAL7dKVxxfEybAFIacumC0HyAIJWtbZDcfl6mnP3qmrGbIo8PebzwpOGCkDMFu
NS4aC+dmqJQSqfl2yufNYbr+2eZGoPmhE206qfIL0KBM3Cch8M2RytEXHjyBCH4s
u5SGaOALrvlM5zWADoTWyhd6PEg9EWEHkl9vo2MkFYq90o7/VIzWQBX15H5uCsYJ
wIyI9Itq6I/JD32gR2i0
=lqgz
-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/b87bc9fb-cdff-99a7-56a0-77058ad24850%40qubes-os.org.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Bug - Qubes fails to boot if a USB Audio device is connected to the PC

[Grzesiek Chodzicki]

I know that this sounds rather bizarre, but my Qubes instance consistently gets 
stuck after GRUB menu if a USB Audio device is connected to the computer. So 
far I have a 3/3 repro rate on that. What type of logs/information should I 
gather from my machine in order to troubleshoot that?
XL dmesg does print a RMRR warning about USB controllers

Qubes 3.2
Kernel 4.8.12-12
I use a sys-usb AppVM with all controllers hidden from Dom0.

-- 
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/bc169684-65b8-4782-8acd-6b5553c7dbc3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Bug or Feature? DispVM inherits settings from calling VM

[Andrew David Wong]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

On 2016-10-12 01:50, Robert Mittendorf wrote:
> If I use /usr/bin/qvm-run to open an application in an disposible VM, the 
> dispVM inherits some setings from the calling VM
> 
> example: I use
> 
> /usr/bin/qvm-run --dispvm firefox
> 
> In work-VM. My work-VM is configured to allow intranet IPs only. The starting 
> dispVM is blue like the work VM, even though normal DispVMs are red.
> 
> Also the firewall rules (intranet only) are inherited from the work VM.
> 
> 
> mit freundlichem Gruß,
> 
> Robert Mittendorf
> 

Yes, these are intentional DispVM design decisions.

However, there are also plans to allow DispVMs to inhert the NetVM of the 
calling VM without also inheriting its firewall rules:

https://github.com/QubesOS/qubes-issues/issues/1296

- -- 
Andrew David Wong (Axon)
Community Manager, Qubes OS
https://www.qubes-os.org
-BEGIN PGP SIGNATURE-

iQIcBAEBCgAGBQJX/rG6AAoJENtN07w5UDAwEbIP/1V6cb+BIbJwF1Mpw30bC5T6
ObOJozl40vJN+CZIA1PKEKJV2ELqPgWg+SO9xaawPPz4YvzRiBhi+oxhBUTekCpx
NRMpqWHAJU4Vr6KHM/H7K0XRN8UexFDYF9giyVgaboBupNs/k+bOpyeio6Ak1KVc
6vW1gL91ea84UxupNqZcDeDUn4fFvQ9H/ULLvzhbcyOHXh/LIH1JnFfpnLpnRICH
h5moGm+NX5Ssq8A+oO9uigpo7mpqvFstUVbTqL6htvdxPZ2RxlAL2Q8dk51nGmMN
N9SRJUDGqdB1a6A8UOWSS6SVy+6/V7mTwM2tZbKtr+J2XsFTqgu1SuuMEW4IOax0
Zg/7h3ritkixrxh2l8Ll4uREYlS9rCVnwjWGYJ1PmVMmg/0G37RTKpHnlsCPT/sT
9lD14UCYo2nuZGJYJpoc+d1UwICJpIoWw/84XC1V3Z0LaZ+UVDJ7a46s5I+EVWYL
2P9RK8HFlaAIQbWMfGMjc7Thi99SMg8KNNpS7ndOLzc7l/sQvjQ1ZbrCSPYQfF0t
+YlJYv4IkT3+bAKAuj1ra0ftiL7aCugOWMM+bcL2slGDTBEDkB3H8XEFGMVJYvlJ
XU5/cbWdIDi41sJgdql1fvMcp2jHAQ6W48Myq+5uA0DARfprQSHH+TNRkZbMDr7U
BYu3KN8wyiAdsvmgR0+p
=O5PZ
-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/3f4415cd-3188-5ac7-0e53-82a284670b16%40qubes-os.org.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Bug or Feature? DispVM inherits settings from calling VM

[Robert Mittendorf]

If I use /usr/bin/qvm-run to open an application in an disposible VM, 
the dispVM inherits some setings from the calling VM


example: I use

/usr/bin/qvm-run --dispvm firefox

In work-VM. My work-VM is configured to allow intranet IPs only. The 
starting dispVM is blue like the work VM, even though normal DispVMs are 
red.


Also the firewall rules (intranet only) are inherited from the work VM.


mit freundlichem Gruß,

Robert Mittendorf

--
M. Sc. Informatik Robert Mittendorf

DigiTrace GmbH - Kompetenz in IT-Forensik
Geschäftsführer: Alexander Sigel, Martin Wundram
Registergericht Köln, HR B 72919
USt-IdNr: DE278529699

Zollstockgürtel 59, 50969 Köln
Telefon: 0221-6 77 86 95-2
Website: www.DigiTrace.de
E-Mail: i...@digitrace.de

Haben Sie schon den DigiTrace-Newsletter abonniert?
http://www.digitrace.de/de/service/newsletter

DigiTrace ist Partner der Allianz für Cyber-Sicherheit
sowie Mitglied im nrw.units Netzwerk für IT-Sicherheit:
  https://www.allianz-fuer-cybersicherheit.de
  http://www.nrw-units.de/netzwerk/

--
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/9cd098fc-3e92-999c-40a0-0449b5612e0e%40digitrace.de.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] [bug] Inter-VM Copy/Paste Broken After Long Uptime

[Drew White]

On Thursday, 21 July 2016 08:28:29 UTC+10, Andrew David Wong  wrote:
> > Also, are there other known problems with running Qubes with a such a 
> > "long" uptime?
> > 
> 
> This and the Qubes Manager memory leak are the only two I know of.
> 
> https://github.com/QubesOS/qubes-issues/issues/860
> 
> (Note that the latter was recently fixed, but the package is in the R3.2
> dom0 testing repo.)

"Testing REPO" != "fixed"
"Testing REPO" == "is it fixed?"

I hope that it does get fixed sometime soon.

-- 
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/3a3f093c-b81a-425a-8e2c-6d8b2c638372%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] [bug] Inter-VM Copy/Paste Broken After Long Uptime

[Andrew David Wong]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

On 2016-07-20 01:23, Holger Levsen wrote:
> Hi,
> 
> On Tue, Jul 19, 2016 at 09:54:19PM +0200, Marek Marczykowski-Górecki 
> wrote:
>>> I have one particular Qubes instance with an uptime >60 days.  Aside
> [...]
>>> Any suggestions on how to debug?
>> 
>> Yes, remove /var/run/qubes/qubes-clipboard.bin.xevent
>> 
>> The file contains X event timestamp of last copy/paste operation (to 
>> avoid some race conditions). But this counter overflows after some time 
>> (a month or so) and our code do not handle this case.
> 
> Is this a known issue tracked in github? If not I think it should be…
> 

Thanks. Tracking:

https://github.com/QubesOS/qubes-issues/issues/2189

> Also, are there other known problems with running Qubes with a such a 
> "long" uptime?
> 

This and the Qubes Manager memory leak are the only two I know of.

https://github.com/QubesOS/qubes-issues/issues/860

(Note that the latter was recently fixed, but the package is in the R3.2
dom0 testing repo.)

- -- 
Andrew David Wong (Axon)
Community Manager, Qubes OS
https://www.qubes-os.org
-BEGIN PGP SIGNATURE-

iQIcBAEBCgAGBQJXj/r6AAoJENtN07w5UDAwBdsP/0XYrQ1AQHqSBAked7uoCUte
HO7261q/XJsgdRBlrpL4O/0tPOU6jU8OV7u5+8nMLEByvNpvqP1li8EfX9/es3Bg
oo3veDr6H72HDnw7cFw+KxnkKiAIAxbBuF4xBgLlIh0shOhpqTjdfu+8TCdCF9mS
7T8Ycgac5uYZ+NXbvlrMVD9uiiJK6Wq1aidjYGx1hLWkunbPSXbTKXogP4Z6MvrI
hDT+xt4CBup4dWFofkguACrngrbmrgoyrH+BNicDCezGHgtOEikS/fK/VMuZFU/Y
6LaFBLgJSAqvbIBCIfUrxtBB8zp7Z7T1UqYwkY1AZwpoPiAVV99Sqn0Zym3mjzPa
I+8qHDK8vf/eoV/VvjJ2439MpNed2g8iw7jT1vCDfEwcciMu1ah0gVXoCC7czpac
GxX7x9Xhq+aBqYyLcSHf35bYnGf/sEmzePDAhH1UuaBDPOpaMzsdBOToNVH4dI31
28mczL7+iew/ToR04tFWzLkTYgiOXgSa/A5j0PBtz5oEFAj0u0/wLiDEYwV9wukI
9xYLIBa6ihkTO2PyvvMkfHrsWEISnWDRsbbDqH+ikW47NtC1EgT3tP+uSnhm2nLc
+1oBYNXrf+D9p8z6OHDmhi+WJbJW1+XMsvFwYKhvra/NusvY1FvifPgVw6NJhQFx
eV8aRbYbuHW4au5tuN9g
=qHcC
-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/f63eceba-b76e-cff3-3887-71ae5d11656f%40qubes-os.org.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] [bug] Inter-VM Copy/Paste Broken After Long Uptime

[Holger Levsen]

Hi,

On Tue, Jul 19, 2016 at 09:54:19PM +0200, Marek Marczykowski-Górecki wrote:
> > I have one particular Qubes instance with an uptime >60 days.  Aside
[...]
> > Any suggestions on how to debug?
> 
> Yes, remove /var/run/qubes/qubes-clipboard.bin.xevent
> 
> The file contains X event timestamp of last copy/paste operation (to
> avoid some race conditions). But this counter overflows after some time
> (a month or so) and our code do not handle this case.

Is this a known issue tracked in github? If not I think it should be…

Also, are there other known problems with running Qubes with a such a
"long" uptime?


-- 
cheers,
Holger

-- 
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/20160720082352.GA6729%40layer-acht.org.
For more options, visit https://groups.google.com/d/optout.


signature.asc
Description: Digital signature

Re: [qubes-users] [bug] Inter-VM Copy/Paste Broken After Long Uptime

[Andrew]

Marek Marczykowski-Górecki:
> On Tue, Jul 19, 2016 at 01:13:22PM +, Andrew wrote:
>> Hello,
> 
>> I have one particular Qubes instance with an uptime >60 days.
>> Aside from needing to occasionally restart Qubes Manager to deal
>> with the memory leak problem, this works fine.
> 
>> However, recently, I have become unable to copy and paste between
>> VMs. Pressing the key combination appears to do nothing.  FWIW, 
>> /var/run/qubes/qubes-clipboard.bin and 
>> /var/run/qubes/qubes-clipboard.bin.source are both 0-sized files 
>> (presumably) dated to back when inter-VM copy/paste stopped
>> working.
> 
>> Any suggestions on how to debug?
> 
> Yes, remove /var/run/qubes/qubes-clipboard.bin.xevent
> 
> The file contains X event timestamp of last copy/paste operation
> (to avoid some race conditions). But this counter overflows after
> some time (a month or so) and our code do not handle this case.
> 
> 

I see, thanks.

Andrew

-- 
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/7b1ef5f1-5d55-74d7-80b0-511b370751df%40riseup.net.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] [bug] Inter-VM Copy/Paste Broken After Long Uptime

[Marek Marczykowski-Górecki]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

On Tue, Jul 19, 2016 at 01:13:22PM +, Andrew wrote:
> Hello,
> 
> I have one particular Qubes instance with an uptime >60 days.  Aside
> from needing to occasionally restart Qubes Manager to deal with the
> memory leak problem, this works fine.
> 
> However, recently, I have become unable to copy and paste between VMs.
> Pressing the key combination appears to do nothing.  FWIW,
> /var/run/qubes/qubes-clipboard.bin and
> /var/run/qubes/qubes-clipboard.bin.source are both 0-sized files
> (presumably) dated to back when inter-VM copy/paste stopped working.
> 
> Any suggestions on how to debug?

Yes, remove /var/run/qubes/qubes-clipboard.bin.xevent

The file contains X event timestamp of last copy/paste operation (to
avoid some race conditions). But this counter overflows after some time
(a month or so) and our code do not handle this case.

- -- 
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

iQEcBAEBCAAGBQJXjoVrAAoJENuP0xzK19csJOwH/iXTl3LwfmhG756g8IwhBSs8
uaoSAh3LIU46P1Fjy0f4+0hZnl6EHfvmKY0YkcX2Kq6ZqBlHXdfkcooCGGqLYilX
5NKD5hmGcVPtAcgZ1eRADXxyUBoMgeCEoQo95M7/Y4dQFsvJbp+pyX+zASRL9YZf
G7LN9yRG29EjRnWSi2briSKYyoTP4Wn3euF4USlPZ67k01uVNLigCcurzPGKw2HT
z+UHtqMPJYFQ/eajJBjENwyozLRRNa3G2wgte7M8eU3rWAbQmIeJlY6QLo7E4Tba
oYve8pRem8/vD4mIKBavfc6wzaG9MvdpUlc3iPWt9+W3FEXbk5rLkBzI0Y9/mhw=
=qQCd
-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/20160719195419.GS1161%40mail-itl.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] [bug] Inter-VM Copy/Paste Broken After Long Uptime

[Andrew]

Hello,

I have one particular Qubes instance with an uptime >60 days.  Aside
from needing to occasionally restart Qubes Manager to deal with the
memory leak problem, this works fine.

However, recently, I have become unable to copy and paste between VMs.
Pressing the key combination appears to do nothing.  FWIW,
/var/run/qubes/qubes-clipboard.bin and
/var/run/qubes/qubes-clipboard.bin.source are both 0-sized files
(presumably) dated to back when inter-VM copy/paste stopped working.

Any suggestions on how to debug?

Andrew

-- 
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/9f00af78-1a39-1298-441a-a7485e88957f%40riseup.net.
For more options, visit https://groups.google.com/d/optout.