Deleted Pulseaudio from dom0 and broke every VM

312 views
Skip to first unread message

rollingelectron

unread,
Jul 2, 2018, 1:19:20 PM7/2/18
to qubes...@googlegroups.com
R3.2, executing 'sudo dnf remove pulseaudio' in dom0 removes:
pulseaudio, pulseaudiomodule-conf, paprefs, qubes-gui-dom0, rtkit, soxr, speexdsp and webrtc-audio-processing
this stopped any vm from starting, how can I reinstall pulseaudio and the dependencies in dom0 when the netvm and sys-usb vm wont start?

Marek Marczykowski-Górecki

unread,
Jul 2, 2018, 1:58:30 PM7/2/18
to rollingelectron, qubes...@googlegroups.com
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
You should be able to start netvm with qvm-start --no-guid. And the same
for firewallvm. Then, qubes-dom0-update should work, so you can use it
to re-install those packages.

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

iQEzBAEBCAAdFiEEhrpukzGPukRmQqkK24/THMrX1ywFAls6Z78ACgkQ24/THMrX
1ywO2Af+MIS4uo7CyOby5Ji33Vmj2cCLFSAh+AobTc8a8VxbjHUVqCcgJpGzJLUS
XQJEqHMqBRt3qYU8qmxY/Qmi0JVjqlZRuRHcb/D9fTujGshG6mv/bEMAeTLT4AEW
nmddiS4ZPycaJSynT/uA7Dz7OtWMVctCbdpEAqxwdW6+Is3rlonmE/iUpu+HZtyp
fdnGA8qtB6VDGQYZqZwR3BXVmPIILzk8NkhgJEHo4KEHA6lN7CIO8c9CUj7Dcz0n
jf5yZOZ7TQjeSY11Ne1HIXGBy0tBRb3roCLyMJHnW8vuon3CyHtE99Qh90g7nLlk
tz1SCz91cFqWkjLIAv5yB5exMyxHSQ==
=tJFa
-----END PGP SIGNATURE-----

rolling electron

unread,
Jul 6, 2018, 2:41:44 PM7/6/18
to qubes-users
The VM stays on the yellow icon and doesn't start. Then trying 'sudo qubes-dom0-update pulseaudio' shows error, cannot start guid.

rolling electron

unread,
Jul 6, 2018, 2:42:39 PM7/6/18
to qubes-users
On Monday, July 2, 2018 at 6:58:30 PM UTC+1, Marek Marczykowski-Górecki wrote:
Is there another way to start VMs with no guid?
Message has been deleted

rolling electron

unread,
Jul 6, 2018, 3:13:38 PM7/6/18
to qubes-users
On Monday, July 2, 2018 at 6:58:30 PM UTC+1, Marek Marczykowski-Górecki wrote:
Can a USB be attached to dom0?

awokd

unread,
Jul 6, 2018, 4:37:33 PM7/6/18
to rolling electron, qubes-users
On Fri, July 6, 2018 7:13 pm, rolling electron wrote:

> Can a USB be attached to dom0?

It can, but not normally recommended. However, it might be the quickest
option at this point if you wanted to backup your VMs, reinstall, then
restore.


rolling electron

unread,
Jul 7, 2018, 2:21:58 AM7/7/18
to qubes-users

any ideas on how to do this?

rolling electron

unread,
Jul 7, 2018, 2:25:54 AM7/7/18
to qubes-users
On Friday, July 6, 2018 at 9:37:33 PM UTC+1, awokd wrote:

wouldn't it be easier to download the dependencies and install them with a usb in dom0?

Sven Semmler

unread,
Jul 7, 2018, 2:44:23 AM7/7/18
to qubes...@googlegroups.com
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On 07/07/2018 01:21 AM, rolling electron wrote:
> any ideas on how to do this?

See https://www.qubes-os.org/doc/usb/ under "Removing a USB qube"

Basically:

1) remove USB qube
2) remove "rd.qubes.hide_all_usb" from your boot config
3) restart computer

/Sven
-----BEGIN PGP SIGNATURE-----

iQIzBAEBCAAdFiEE18ry22WNibwI1qeq2m4We49UH7YFAltAYawACgkQ2m4We49U
H7aXMxAAxkJ22RcHNad5PWffKApcrWET9oJnn8eoLhpAzwClV6e/nsjzWEz/rQkU
FIInfCUB6l/8P/oN6lypQiatOXXmBpZ9b6x9czdNfktC5jH3s+hKy68YsZ/ACv4e
QoR8GaYJQy3zujio+kN4dTALsS24Gx1GtaxpScDL/A7gju8bYogUge6wTEr/5VSq
XGtklmdiOofmsyOGpsJSeVoRzhgKVCnnP8iJxmvoPAaY7uSSBbgbEc69DlfdQLpD
W/G/2qtr5vEOeQrJ7CA7OExI9+ZAEb329WcSArZpXVBm5b36ZAFMrcSiUKncWIbJ
UE9+F3fEi7+mGgZMDrmVdfdOkkSDRt7LMw2ws/M+cMatSt73LMSr209EAQej2sMq
nzu07bPacLzntbw2SRGWNgUD7mcaxv1k2k0f0EzPeunPUfs/RggGi47DRS4YETBs
5khGV8/MTAEPl9TRTAy+7i0RVsxw9LOVxU1M3r4Gc2852TJu5OpeuhG0TwDzTtRh
TwTt/oSVG/fAHItMWadWfa92QINSqu6KHoYG6bksOuF2jzUNVaIIxxb/Gkjrzx35
2JGtBDxf0GSp0IM1SLI4I/YhHaJr7Dzw0KxzADs0KKDWyt/B7czUdJIBRpf4Gh2A
wWf4t5FCitVtOuf5dWOQVNloF9/sBmtjVhXKYhyAQmjDGydhXVE=
=YtVn
-----END PGP SIGNATURE-----

Kristian Elof Sørensen

unread,
Jul 14, 2018, 4:10:44 PM7/14/18
to qubes...@googlegroups.com
Quite possible related:

Qubes 3.2

Fedora-28 and Fedora-27 templates

When updating the template, eg. by using "update vm" in Qubes-VM
manager, a pulseaudio 11 vs 12 conflict stops the update. See full
error message further below.

If the update is forced using --allowerasing, any vm using the updated
template refuses to start, stating: "cannot start qubes-guid!"

Kristian


Last metadata expiration check: 0:08:35 ago on Sat 14 Jul 2018 09:56:58 PM CEST.
Error:
Problem 1: package qubes-gui-vm-3.2.22-1.fc27.x86_64 requires pulseaudio = 11.1, but none of the providers can be installed
- cannot install both pulseaudio-12.0-3.fc27.x86_64 and pulseaudio-11.1-15.fc27.x86_64
- cannot install both pulseaudio-11.1-3.fc27.x86_64 and pulseaudio-12.0-3.fc27.x86_64
- cannot install the best update candidate for package qubes-gui-vm-3.2.22-1.fc27.x86_64
- cannot install the best update candidate for package pulseaudio-11.1-15.fc27.x86_64
Problem 2: package qubes-vm-dependencies-3.2.3-1.fc27.noarch requires qubes-gui-vm, but none of the providers can be installed
- package qubes-gui-vm-3.2.22-1.fc27.x86_64 requires pulseaudio = 11.1, but none of the providers can be installed
- package pulseaudio-11.1-15.fc27.x86_64 requires pulseaudio-libs(x86-64) = 11.1-15.fc27, but none of the providers can be installed
- package pulseaudio-11.1-3.fc27.x86_64 requires pulseaudio-libs(x86-64) = 11.1-3.fc27, but none of the providers can be installed
- cannot install both pulseaudio-libs-12.0-3.fc27.x86_64 and pulseaudio-libs-11.1-15.fc27.x86_64
- cannot install both pulseaudio-libs-11.1-3.fc27.x86_64 and pulseaudio-libs-12.0-3.fc27.x86_64
- cannot install the best update candidate for package qubes-vm-dependencies-3.2.3-1.fc27.noarch
- cannot install the best update candidate for package pulseaudio-libs-11.1-15.fc27.x86_64
Problem 3: problem with installed package qubes-gui-vm-3.2.22-1.fc27.x86_64
- package qubes-gui-vm-3.2.22-1.fc27.x86_64 requires pulseaudio = 11.1, but none of the providers can be installed
- cannot install both pulseaudio-12.0-3.fc27.x86_64 and pulseaudio-11.1-15.fc27.x86_64
- cannot install both pulseaudio-11.1-3.fc27.x86_64 and pulseaudio-12.0-3.fc27.x86_64
- package pulseaudio-module-bluetooth-12.0-3.fc27.x86_64 requires libpulsecore-12.0.so()(64bit), but none of the providers can be installed
- cannot install the best update candidate for package pulseaudio-module-bluetooth-11.1-15.fc27.x86_64
Problem 4: problem with installed package qubes-vm-dependencies-3.2.3-1.fc27.noarch
- package qubes-vm-dependencies-3.2.3-1.fc27.noarch requires qubes-gui-vm, but none of the providers can be installed
- package qubes-gui-vm-3.2.22-1.fc27.x86_64 requires pulseaudio = 11.1, but none of the providers can be installed
- cannot install both pulseaudio-12.0-3.fc27.x86_64 and pulseaudio-11.1-15.fc27.x86_64
- cannot install both pulseaudio-11.1-3.fc27.x86_64 and pulseaudio-12.0-3.fc27.x86_64
- package pulseaudio-module-x11-12.0-3.fc27.x86_64 requires libpulsecore-12.0.so()(64bit), but none of the providers can be installed
- cannot install the best update candidate for package pulseaudio-module-x11-11.1-15.fc27.x86_64
(try to add '--allowerasing' to command line to replace conflicting packages or '--skip-broken' to skip uninstallable packages)
Done.
Press Enter to shutdown the template, or Ctrl-C to just close this window

Stuart Perkins

unread,
Jul 14, 2018, 4:26:50 PM7/14/18
to qubes...@googlegroups.com
Same problem. I am pretty much stuck not being able to update the fedora templates due to this.

Is there a work-a-round besides just not updating them?

code9n

unread,
Jul 15, 2018, 6:50:16 AM7/15/18
to qubes-users
Also same problem, and I also crashed fedora-27 by using --allowerasing with the pulse audio update - so the guid wouldn't start.
Got the fedora-27 template back with:

$ sudo qubes-dom0-update qubes-template-fedora-27

From https://www.qubes-os.org/doc/templates/fedora/

but I'm just not trying to update fedora-27 now and looking for a workaround, too....

cubit

unread,
Jul 17, 2018, 9:35:01 AM7/17/18
to Qubes Users, Marek Marczykowski-Górecki, Andrew David Wong
14. Jul 2018 20:26 by perkins...@gmail.com:

On Sat, 14 Jul 2018 22:10:38 +0200
Kristian Elof Sørensen <kris...@elof.dk> wrote:

>Quite possible related:
>Qubes 3.2
>Fedora-28 and Fedora-27 templates
>When updating the template, eg. by using "update vm" in Qubes-VM
>manager, a pulseaudio 11 vs 12 conflict stops the update. See full
>error message further below.
>If the update is forced using --allowerasing, any vm using the updated
>template refuses to start, stating: "cannot start qubes-guid!"
> Kristian

 

Same problem. I am pretty much stuck not being able to update the fedora templates due to this.


Is there a work-a-round besides just not updating them?



Do the Qubes Devs have any suggestions for how to get Fedora templates working again?  

Had to roll back to a fresh fedora28 template but now can't update it because doing so breaks it hard and it won't start.


Marek Marczykowski-Górecki

unread,
Jul 17, 2018, 9:40:28 AM7/17/18
to cubit, Qubes Users, Andrew David Wong
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On Tue, Jul 17, 2018 at 03:34:56PM +0200, cubit wrote:
> 14. Jul 2018 20:26 by perkins...@gmail.com <mailto:perkins...@gmail.com>:
There is already updated pulseaudio-qubes package (part of gui-agent-linux
component) in testing repository:
R3.2: https://github.com/QubesOS/updates-status/issues/589
R4.0: https://github.com/QubesOS/updates-status/issues/586

Will be moved to stable in a week.
Until then, avoid using --allowerasing option (or enable testing
repository[1]), dnf will skip conflicting
packages.

[1] https://www.qubes-os.org/doc/software-update-vm/#testing-repositories

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

iQEzBAEBCAAdFiEEhrpukzGPukRmQqkK24/THMrX1ywFAltN8cYACgkQ24/THMrX
1ywgFAf/VB0JgNoHtJX//yP7+geqmssgHmiI5CYJOZ1e0infqKLV4XvcvGVSaZPy
ObHBmZdI8pn8rgrkmpTuc2RKvvA4kmP5bPxMcJtPWYvV8G3s/kXK8zBhz5pj4Kcl
a9F3ZP6GmzIeM+7xOknpBFoZ+l236h5j7cl+KKfAhCZtl3tZxKkY3/GhBJDnPWXX
0dCs87VC0qIqqiFzUAsq6SO8WaX5wcsXzlC2WA9Tz/y0hkN0pYk0363qvU/qHHrI
fK4XSJLHRtzeU0d2I4eOdeu36JYLKYJd7K4XzXMYtkNu6TSMGseuQ1QCEj1SYBSf
iYZovj+wImC2X2mM3mQCJLYi7wFsdQ==
=hRpR
-----END PGP SIGNATURE-----

cubit

unread,
Jul 31, 2018, 7:16:50 AM7/31/18
to Marek Marczykowski-Górecki, Qubes Users
17. Jul 2018 13:40 by marm...@invisiblethingslab.com:
On Tue, Jul 17, 2018 at 03:34:56PM +0200, cubit wrote:
Do the Qubes Devs have any suggestions for how to get Fedora templates working again?  

Had to roll back to a fresh fedora28 template but now can't update it because doing so breaks it hard and it won't start.

There is already updated pulseaudio-qubes package (part of gui-agent-linux
component) in testing repository:
R3.2: https://github.com/QubesOS/updates-status/issues/589
R4.0: https://github.com/QubesOS/updates-status/issues/586

Will be moved to stable in a week.
Until then, avoid using --allowerasing option (or enable testing
repository[1]), dnf will skip conflicting
packages.


I have the following installed now


Name         : qubes-gui-agent-xfce
Version      : 3.2.23
Release      : 1.fc28


Is it just a matter of running  dnf --allowerasing  to fix the conflicts or is something else needed?




cubit

unread,
Jul 31, 2018, 7:41:33 AM7/31/18
to cubit, Marek Marczykowski-Górecki, Qubes Users
31. Jul 2018 11:16 by cu...@tutanota.com:
17. Jul 2018 13:40 by marm...@invisiblethingslab.com:
On Tue, Jul 17, 2018 at 03:34:56PM +0200, cubit wrote:
Do the Qubes Devs have any suggestions for how to get Fedora templates working again?  

Had to roll back to a fresh fedora28 template but now can't update it because doing so breaks it hard and it won't start.

There is already updated pulseaudio-qubes package (part of gui-agent-linux
component) in testing repository:
R3.2: https://github.com/QubesOS/updates-status/issues/589
R4.0: https://github.com/QubesOS/updates-status/issues/586

Will be moved to stable in a week.
Until then, avoid using --allowerasing option (or enable testing
repository[1]), dnf will skip conflicting
packages.


I have the following installed now


Name         : qubes-gui-agent-xfce
Version      : 3.2.23
Release      : 1.fc28


Is it just a matter of running  dnf --allowerasing  to fix the conflicts or is something else needed?



to answer my own question, it's still broken on R3.2 if you do "dnf update --best --allowerasing"


Does anyone know the best way to fix this long term?



Steve Coleman

unread,
Jul 31, 2018, 11:27:43 AM7/31/18
to Qubes Users
On 07/31/18 07:41, cubit wrote:
> 31. Jul 2018 11:16 by cu...@tutanota.com <mailto:cu...@tutanota.com>:
>
> 17. Jul 2018 13:40 by marm...@invisiblethingslab.com
> <mailto:marm...@invisiblethingslab.com>:
>

>
> to answer my own question, it's still broken on R3.2 if you do "dnf
> update --best --allowerasing"
>
>
> Does anyone know the best way to fix this long term?

I'm no expert in RPM management, but the core of the issue appears to be
this:

A) pulseaudio-qubes-4.0.11-1.fc28.x86_64 requires = pulseaudio-*12.0*
B) pulseaudio Version *12.2-1* is available already
C) pulseaudio Version 12.0 is *not available anywhere*
D) Qubes package pulseaudio-qubes apparently does *not* accept anything
greater than 12.0 for some reason.
E) Any attempt to use --allow-erasing will badly break your system by
permanently removing a necessary qubes component(s) (e.g. gui-agent or
pulseaudio)

I believe that the pulseaudio-qubes-4.0.11-1 package needs have its
dependencies updated to permit pulseaudio >= 12.0 to satisfy its own
requirements. If republishing pulseaudio-qubes with the same version
number is not possible then a minor version bump would do the trick.

The pulseaudio version numbering is already ahead of qubes requirement,
and this "version gap" is only going to get wider until pulseaudio-qubes
own dependency requirement is updated to catch up to the current version
in the public repository, unless they want to publish their own version
of it in the qubes repository (that could get messy).

Why the fedora public repository skipped 12.0 altogether I have no clue,
but one of them needs to change. Either the fedora repository needs to
back populate itself with version 12.0, even though 12.2-1 is already
available, or the pulseaudio-qubes package needs to be updated to
include dependencies up to and including 12.2.*


btw - After some update testing I lost my sound again yesterday and
recovered it by:

$ sudo dnf downgrade pulseaudio-qubes
# then catch up on regular patches, ignoring broken
$ sudo dnf update

My dependencies are still broken, but at least I have my sound back.


Stuart Perkins

unread,
Jul 31, 2018, 1:42:23 PM7/31/18
to qubes...@googlegroups.com
Interestingly enough, the last time I tried to upgrade the fedora-28 template {--allowerasing --best) (Qubes 3.2), it uninstalled the pulseaudio-gui etc... I reinstalled it before shutting down the template, and sys-net and sys-firewall came up just fine. There are definitely some dependency issues here.

Stuart Perkins

unread,
Aug 2, 2018, 11:23:04 AM8/2/18
to qubes...@googlegroups.com
Still having this problem trying to upgrade the fedora-28 template on Qubes 3.2.

[user@fedora-28 ~]$ sudo dnf upgrade
Last metadata expiration check: 0:14:59 ago on Thu 02 Aug 2018 10:03:52 AM CDT.
Dependencies resolved.

Problem 1: cannot install the best update candidate for package qubes-gui-vm-3.2.22-1.fc28.x86_64
- nothing provides pulseaudio = 12.0 needed by qubes-gui-vm-3.2.23-1.fc28.x86_64
Problem 2: package qubes-vm-dependencies-3.2.3-1.fc28.noarch requires qubes-gui-vm, but none of the providers can be installed
- package qubes-gui-vm-3.2.22-1.fc28.x86_64 requires pulseaudio = 11.1, but none of the providers can be installed
- cannot install both pulseaudio-12.2-1.fc28.x86_64 and pulseaudio-11.1-18.fc28.x86_64
- cannot install both pulseaudio-11.1-18.fc28.x86_64 and pulseaudio-12.2-1.fc28.x86_64
- cannot install the best update candidate for package qubes-vm-dependencies-3.2.3-1.fc28.noarch
- cannot install the best update candidate for package pulseaudio-11.1-18.fc28.x86_64
- nothing provides pulseaudio = 12.0 needed by qubes-gui-vm-3.2.23-1.fc28.x86_64
Problem 3: problem with installed package qubes-gui-vm-3.2.22-1.fc28.x86_64
- package qubes-gui-vm-3.2.22-1.fc28.x86_64 requires pulseaudio = 11.1, but none of the providers can be installed
- package pulseaudio-11.1-18.fc28.x86_64 requires libpulsecommon-11.1.so()(64bit), but none of the providers can be installed
- cannot install both pulseaudio-libs-12.2-1.fc28.x86_64 and pulseaudio-libs-11.1-18.fc28.x86_64
- cannot install both pulseaudio-libs-11.1-18.fc28.x86_64 and pulseaudio-libs-12.2-1.fc28.x86_64
- cannot install the best update candidate for package pulseaudio-libs-11.1-18.fc28.x86_64
- nothing provides pulseaudio = 12.0 needed by qubes-gui-vm-3.2.23-1.fc28.x86_64
Problem 4: problem with installed package qubes-vm-dependencies-3.2.3-1.fc28.noarch
- package qubes-vm-dependencies-3.2.3-1.fc28.noarch requires qubes-gui-vm, but none of the providers can be installed
- package qubes-gui-vm-3.2.22-1.fc28.x86_64 requires pulseaudio = 11.1, but none of the providers can be installed
- cannot install both pulseaudio-12.2-1.fc28.x86_64 and pulseaudio-11.1-18.fc28.x86_64
- cannot install both pulseaudio-11.1-18.fc28.x86_64 and pulseaudio-12.2-1.fc28.x86_64
- package pulseaudio-module-bluetooth-12.2-1.fc28.x86_64 requires libpulsecore-12.2.so()(64bit), but none of the providers can be installed
- cannot install the best update candidate for package pulseaudio-module-bluetooth-11.1-18.fc28.x86_64
- nothing provides pulseaudio = 12.0 needed by qubes-gui-vm-3.2.23-1.fc28.x86_64

Reply all
Reply to author
Forward
0 new messages