Troubleshooting with Pipewire after uncompleted update

[Diego Iván Martínez Escobar]

Greetings, everyone,

Yesterday, while updating my system, the power went out, and the process
did not complete. Initially, the system could not get into the gnome-shell.
I could solve this by completing the update by booting it into the text
terminal.

When I could finally use the gnome-shell, the audio did not work. Switching
to Pulseaudio can solve the problem, but I noticed that Pipewire config
file broke, it was empty (I thought this was the reason Pipewire was not
working).
I installed back again Pipewire, and DNF created a config file by default.
When rebooting and logging back, it did not work either, a solution I found
was running Pipewire from the terminal and specifying the config file with

pipewire -c /usr/share/pipewire/pipewire.conf

And it made audio work back again (finally!). Still, I would like to know
if it is possible to get it running just when logged in. Any help or
comments are welcomed.

Thanks for reading!

[George N. White III]

On Sun, 23 May 2021 at 22:25, Diego Iván Martínez Escobar <

Post by Diego Iván Martínez Escobar
Greetings, everyone,
Yesterday, while updating my system, the power went out, and the process
did not complete. Initially, the system could not get into the gnome-shell.
I could solve this by completing the update by booting it into the text
terminal.

Power failing during an update/install is not good.

Post by Diego Iván Martínez Escobar
When I could finally use the gnome-shell, the audio did not work.
Switching to Pulseaudio can solve the problem, but I noticed that Pipewire
config file broke, it was empty (I thought this was the reason Pipewire was
not working).
I installed back again Pipewire, and DNF created a config file by default.
When rebooting and logging back, it did not work either, a solution I found
was running Pipewire from the terminal and specifying the config file with
pipewire -c /usr/share/pipewire/pipewire.conf
And it made audio work back again (finally!). Still, I would like to know
if it is possible to get it running just when logged in. Any help or
comments are welcomed.

There may be many other configuration glitches. Even if there are
only a few issues left by the power failure, you can't know if the next
problem is due to a bug in the software or a side-effect of the power
failure.

It is far better if you can be confident that your system is properly
configured, which could require a full install. Debian's package
manager does have a "configuration still needed" status for packages
that were installed by didn't complete post-install configuration. Maybe
a dnf guru knows of something similar for Fedora.

[stan via users]

On Mon, 24 May 2021 09:02:09 -0300

On Sun, 23 May 2021 at 22:25, Diego Iván Martínez Escobar <

Post by Diego Iván Martínez Escobar
Greetings, everyone,
Yesterday, while updating my system, the power went out, and the
process did not complete. Initially, the system could not get into
the gnome-shell. I could solve this by completing the update by
booting it into the text terminal.

There may be many other configuration glitches. Even if there are
only a few issues left by the power failure, you can't know if the
next problem is due to a bug in the software or a side-effect of the
power failure.
It is far better if you can be confident that your system is properly
configured, which could require a full install. Debian's package
manager does have a "configuration still needed" status for packages
that were installed by didn't complete post-install configuration.
Maybe a dnf guru knows of something similar for Fedora.

I'm no dnf guru, but I would think that a
dnf distr-osync
is the way to go. That will put the system in the latest rational
state. After it completes you should do
rpmconf
to validate any configuration file changes.
_______________________________________________
users mailing list -- ***@lists.fedoraproject.org
To unsubscribe send an email to users-***@lists.fedoraproject.org
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/***@lists.fedoraproject.org
Do not reply to spam on the list, report it: https://pagure.io/f

[stan via users]

On Mon, 24 May 2021 06:15:10 -0700

Post by stan via users
dnf distr-osync

typo, should be
dnf distro-sync
_______________________________________________
users mailing list -- ***@lists.fedoraproject.org
To unsubscribe send an email to users-***@lists.fedoraproject.org
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/***@lists.fedoraproject.org
Do not reply to spam on the list, report it: https://pagure.

[Diego Ivan]

Greetings,

This is what happened recently:

When running distro-sync, DNF notified me that the operation would
remove systemd. To see what was going on with it, I run dnf check |
grep "systemd". It seems there were duplicates, that I removed and now
I could run dnf distro-sync. I applied the missing configuration with
rpmconf (it seems there was a postlogin configuration that was not
applied)

Then, I rebooted and... Still got no audio. I switched to Pulseaudio
back again. I believe I will end up making a fresh Fedora 34 install, I
had already backed up many of my files.

Anyways... Thanks for your help and comments! Trying to fix this issue,
I learned a lot about Pipewire, config files, and also, about DNF by
reading documentation. I will be replying to this thread if I ever
discover something new, in case it is needed.

El lun, 24 de may de 2021 a las 08:26:19 AM, stan via users

Post by stan via users
On Mon, 24 May 2021 06:15:10 -0700

Post by stan via users
dnf distr-osync

typo, should be
dnf distro-sync
_______________________________________________
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
https://fedoraproject.org/wiki/Mailing_list_guidelines
https://pagure.io/fedora-infrastructure

_______________________________________________
users mailing list -- ***@lists.fedoraproject.org
To unsubscribe send an email to users-***@lists.fedoraproject.org
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/***@lists.fedoraproject.org
Do not reply to spam on the list, report it: https://pagure.io/fedora-infra

[stan via users]

On Mon, 24 May 2021 13:54:20 -0500

Post by Diego Iván Martínez Escobar
Greetings,
When running distro-sync, DNF notified me that the operation would
remove systemd. To see what was going on with it, I run dnf check |
grep "systemd". It seems there were duplicates, that I removed and
now I could run dnf distro-sync. I applied the missing configuration
with rpmconf (it seems there was a postlogin configuration that was
not applied)
Then, I rebooted and... Still got no audio. I switched to Pulseaudio
back again. I believe I will end up making a fresh Fedora 34 install,
I had already backed up many of my files.
Anyways... Thanks for your help and comments! Trying to fix this
issue, I learned a lot about Pipewire, config files, and also, about
DNF by reading documentation. I will be replying to this thread if I
ever discover something new, in case it is needed.

The fact that there were duplicate packages installed means that the
update could have been left in an incomplete state for another package.
So, you are probably right to re-install to be sure everything is
correct, and it is certainly easier than looking for the error.

But it might be that the update interrupt isn't the problem, and there
is a bug in pipewire for your system. In that case, you could post
here again, or open a bugzilla against pipewire.
_______________________________________________
users mailing list -- ***@lists.fedoraproject.org
To unsubscribe send an email to users-***@lists.fedoraproject.org
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/***@lists.fedoraproject.org
Do not reply to spam on the list, report it: https://pagure.io/fedora-infr