[qubes-users] Issues updating whonix

2022-12-08 Thread Ulrich Windl

Hi!

When trying to update Whonix, I got these errors:

Updating whonix-gw-16

Error on updating whonix-gw-16: Command '['sudo', 'qubesctl', 
'--skip-dom0', '--targets=whonix-gw-16', '--show-output', 'state.sls', 
'update.qubes-vm']' returned non-zero exit status 20.

whonix-gw-16:
  --
ID: update
  Function: pkg.uptodate
Result: False
   Comment: E: Failed to fetch 
tor+https://deb.kicksecure.com/dists/bullseye/InRelease  Invalid 
response from proxy: HTTP/1.0 500 Unable to connect  Server: 
tinyproxy/1.10.0  Content-Type: text/html  Connection: close [IP: 
127.0.0.1 8082]
E: Some index files failed to download. They have been 
ignored, or old ones used instead.

   Started: 19:43:04.329350
  Duration: 62072.536 ms
   Changes:
  --
ID: notify-updates
  Function: cmd.run
  Name: /usr/lib/qubes/upgrades-status-notify
Result: False
   Comment: Command "/usr/lib/qubes/upgrades-status-notify" run
   Started: 19:44:06.404208
  Duration: 7448.458 ms
   Changes:
--
pid:
1840
retcode:
100
stderr:
stdout:

  Summary for whonix-gw-16
  
  Succeeded: 0 (changed=1)
  Failed:2
  
  Total states run: 2
  Total run time:  69.521 s

Updating whonix-ws-16

Error on updating whonix-ws-16: Command '['sudo', 'qubesctl', 
'--skip-dom0', '--targets=whonix-ws-16', '--show-output', 'state.sls', 
'update.qubes-vm']' returned non-zero exit status 20.

whonix-ws-16:
  --
ID: update
  Function: pkg.uptodate
Result: False
   Comment: E: Failed to fetch 
tor+https://deb.kicksecure.com/dists/bullseye/InRelease  Invalid 
response from proxy: HTTP/1.0 500 Unable to connect  Server: 
tinyproxy/1.10.0  Content-Type: text/html  Connection: close [IP: 
127.0.0.1 8082]
E: Some index files failed to download. They have been 
ignored, or old ones used instead.

   Started: 19:45:31.843086
  Duration: 24016.262 ms
   Changes:
  --
ID: notify-updates
  Function: cmd.run
  Name: /usr/lib/qubes/upgrades-status-notify
Result: False
   Comment: Command "/usr/lib/qubes/upgrades-status-notify" run
   Started: 19:45:55.861625
  Duration: 4671.225 ms
   Changes:
--
pid:
1870
retcode:
100
stderr:
stdout:

  Summary for whonix-ws-16
  
  Succeeded: 0 (changed=1)
  Failed:2
  
  Total states run: 2
  Total run time:  28.687 s

--
Ist that a known problem, or just a temporary failure?

Regards,
Ulrich

--
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/5631f459-b5da-11e2-ed97-4060b99ff5c1%40rz.uni-regensburg.de.


[qubes-users] ALSA/pulseaudio issue?

2022-12-08 Thread Ulrich Windl

Shortly after starting Qubes OS 4.1 I noticed this message in syslog:

Dec 08 20:10:48 dom0 qrexec-policy-daemon[4745]: qrexec: qubes.GetDate+: 
sys-firewall -> @default: allowed to dom0
Dec 08 20:10:48 dom0 pulseaudio[7749]: ALSA woke us up to write new data 
to the device, but there was actually nothing to write.
Dec 08 20:10:48 dom0 pulseaudio[7749]: Most likely this is a bug in the 
ALSA driver 'snd_hda_intel'. Please report this issue to the ALSA 
developers.
Dec 08 20:10:48 dom0 pulseaudio[7749]: We were woken up with POLLOUT set 
-- however a subsequent snd_pcm_avail() returned 0 or another value < 
min_avail.
Dec 08 20:10:48 dom0 qrexec-policy-daemon[4745]: qrexec: 
qubes.WindowIconUpdater+: sys-firewall -> @adminvm: allowed to dom0


Is that a known bug?

Regards,
Ulrich

--
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/c60c89ff-989c-b1f2-42f8-d947fc325d94%40rz.uni-regensburg.de.


[qubes-users] Fedora 35 reaches EOL on 2022-12-13

2022-12-08 Thread Andrew David Wong
Dear Qubes Community,

The Fedora Project has 
[announced](https://lists.fedoraproject.org/archives/list/devel-annou...@lists.fedoraproject.org/thread/OGTVKLX7OXBYCEUQ66UY4YK3T6QHAYW5/)
 that Fedora 35 will reach EOL 
([end-of-life](https://fedoraproject.org/wiki/End_of_life)) on 2022-12-13. We 
strongly recommend that all users 
[upgrade](https://www.qubes-os.org/doc/templates/fedora/#upgrading) their 
Fedora templates and standalones to Fedora 36 no later than 2022-12-13.

We provide fresh Fedora 36 template packages through the official Qubes 
repositories, which you can install in dom0 by following the standard 
[installation 
instructions](https://www.qubes-os.org/doc/templates/fedora/#installing). 
Alternatively, we also provide step-by-step instructions for [performing an 
in-place 
upgrade](https://www.qubes-os.org/doc/templates/fedora/in-place-upgrade/) of an 
existing Fedora template. After upgrading your templates, please remember to 
[switch all qubes that were using the old template to use the new 
one](https://www.qubes-os.org/doc/templates/#switching).

For a complete list of template releases that are supported for your specific 
Qubes release, see our [supported template 
releases](https://www.qubes-os.org/doc/supported-releases/#templates).

Please note that no user action is required regarding the OS version in dom0. 
For details, please see our [note on dom0 and 
EOL](https://www.qubes-os.org/doc/supported-releases/#note-on-dom0-and-eol).


This announcement is also available on the Qubes website:
https://www.qubes-os.org/news/2022/12/08/fedora-35-reaches-eol-on-2022-12-13/

-- 
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/635e14c4-d155-7af8-5dbd-702f45fe6532%40qubes-os.org.