Pipeware issue in KDE after F34->F35
by Miroslav Suchý
I hit the same issue for the second time, therefore I strike coincidence.
I have machine upgraded from F34 to F35 (and actually upgraded every 6 month from Fedora-I-dunno). And after the upgrade
I do not see the sound devices. Therefore there is no sound.
For the first time it magically started working after some time - I have done zilions of things and I am not sure what
makes it work.
Now I have a second notebook where it does not work, and nothing what I have done on the first machine helped so far.
I am asking here, because I am really not sure what component is causing it (pipewire, KDE, something else).
Some data:
* selinux is out as it happens even in permissive mode
* it is KDE environment (I cannot try Gnome)
* systemctl--userrestart pipewire-pulse.service
does not help. And status shows, that it is active and running
* pactl info shows:
... PulseAudio (on PipeWire 0.3.38
...
Default Sink: @DEFAULT_SINK@
Default Target: @DEFAULT_SOURCE@
and when I manually run "wireplumber" it shows:
Default Sink: alsa_output.pci-0000_00_1b.0.analog-stereo
Default Source: alsa_input.pci-0000_00_1b.0.analog-stereo
and the devices appear in KDE and I can play a sound.
Any hints, please?
Miroslav
2 years, 7 months
F36 Change: Retire the NIS(+) user-space utility programs
(System-Wide Change proposal)
by Ben Cotton
https://fedoraproject.org/wiki/Changes/retire_NIS_user_space_utils
== Summary ==
This change is about retiring the ypbind, yp-tools, and ypserv
packages, and removal of the {nis,yp}domainname user-space utility
programs from the hostname package.
== Owner ==
* Name: [[User:besser82 | Björn Esser]]
* Email: besser82(a)fedoraproject.org
== Detailed Description ==
Those utility programs used to be present on virtually any UNIX system
for decades, but are starting to become more and more deprecated.
Also NIS(+) is known for not being secure at all. As we are going to
[https://fedoraproject.org/wiki/Changes/drop_NIS_support_from_PAM
remove the support for NIS(+) in PAM] during this development cycle,
we also should get rid of those.
== Feedback ==
There was some discussion on
[https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.o...
the fedora-devel mailing-list]. Some people are reluctant about the
removal of NIS(+) user-space support, while most are okay with it as
there are more secure alternatives (LDAP, FreeIPA, etc.) available.
The FPL is +1 on doing so.
== Benefit to Fedora ==
With this change we start directing our users and developers to move
away from NIS(+) to secure alternatives like LDAP and/or FreeIPA.
== Scope ==
* Proposal owners:
** Retire the ypbind, yp-tools, and ypserv packages from Fedora.
** Remove the {nis,yp}domainname user-space utility programs from the
hostname package.
* Other developers:
** Test this change.
* Release engineering: [https://pagure.io/releng/issue/10352 #10352]
* Policies and guidelines: N/A (not needed for this Change)
* Trademark approval: N/A (not needed for this Change)
* Alignment with Objectives: N/A
== Upgrade/compatibility impact ==
Users that were relying on support for NIS(+) will need to move to
secure alternatives like LDAP and/or FreeIPA.
== How To Test ==
Check whether the named utility programs are still installed on your
system after upgrading. If they are gone, everything is fine.
== User Experience ==
For some users this change may be a bit disruptive and it may require
some learning curve for switching to alternative solutions.
== Dependencies ==
There are actually no external dependencies.
== Contingency Plan ==
* Contingency mechanism: Unretire the packages and build them for Fedora 36.
* Contingency deadline: At beta freeze.
* Blocks release? Yes.
== Documentation ==
The documentation about those utility programs should be dropped, if
there even is any.
== Release Notes ==
The NIS(+) user-space utility programs have been removed from the distribution.
--
Ben Cotton
He / Him / His
Fedora Program Manager
Red Hat
TZ=America/Indiana/Indianapolis
2 years, 7 months
F37 Change: Ansible 5 (Self-Contained Change proposal)
by Ben Cotton
https://fedoraproject.org/wiki/Changes/Ansible5
== Summary ==
The ansible project has re-organized how they release and distribute
ansible. This change moves Fedora to be in sync with those changes and
retires the old 'ansible classic/2.9.x' package in favor of a
'ansible' package that pulls in ansible-core (the engine) and includes
all the collections in upstream ansible releases.
== Owner ==
* Name: [[User:kevin| Kevin Fenzi]] and [[User:dmsimard]]
* Email: kevin(a)scrye.com, dmsimard(a)redhat.com
== Detailed Description ==
The upstream ansible project found that maintaining a single
monolithic ansible package with everything included was not working
well ([https://www.ansible.com/blog/thoughts-on-restructuring-the-ansible-project
source]). Small changes had to wait for releases, some areas had no
subject matter reviewers, it was difficult to try and handle all the
issues and changes in a timely manner. So, the ansible engine was
split off and then the rest of the content was moved to separate
collections. These collections could then be maintained by communities
that care about that area and could release at their own pace. A
number of collections have agreed to release on the same cadence.
These collections, along with the ansible-core engine comprise a
upstream 'ansible' release.
The engine package (ansible-core) is already in Fedora 35+. Currently
the 'ansible' package is 'ansible classic', ie, the 2.9.x version from
before the reorganization. While Ansible 2.9.x will continue to be
maintained from a security perspective until 2022, it is desireable to
update to the latest release of both ansible-core and ansible in order
to benefit from continued updates, bug fixes and improvements.
This change will modify the existing 'ansible' package to include the
Ansible Collections that are provided in the upstream ansible releases
from PyPi. The ansible package will not include ansible-core but will
have a requirement (dependency) on it.
Having two separate packages will give users the ability to select the
best option based on their needs:
# Install the 'ansible' package to mirror the user experience when
installing ansible from PyPi: it will install ansible-core as well as
the collections as they are included in the upstream ansible release.
# Install just the 'ansible-core' package when no external collections
are necessary
# Install 'ansible-core' and then manually install collections either
from existing [https://koji.fedoraproject.org/koji/search?match=glob&type=package&terms=...
packages in Fedora], from [https://galaxy.ansible.com/ Ansible Galaxy]
or elsewhere.
== Benefit to Fedora ==
* On current upstream releases with bugfixes and enhancements.
* Increases flexibility by allowing users to choose which Ansible
collections to install and where they install it from.
* More rapid improvements for Fedora users.
== Scope ==
* Proposal owners: 'ansible' package needs to be modified for this
change (work is in progress already).
* Other developers: N/A
* Release engineering: N/A
* Policies and guidelines: Possibly policies for packaging collections?
* Trademark approval: N/A (not needed for this Change
* Alignment with Objectives:
== Upgrade/compatibility impact ==
On upgrade, ansible-2.9.x will be replaced by ansible-core + release
collections. Ansible playbooks will continue to run as before.
== How To Test ==
Playbooks that run as expected under Ansible 2.9 may behave
differently under Ansible 5 which effectively updates the
(ansible-core) runtime from 2.9 to 2.12.
Users are encouraged to take a look at the available porting guides
for both Ansible and ansible-core
(https://docs.ansible.com/ansible/devel/porting_guides/porting_guides.html)
and carefully test the behavior of their roles and playbooks in case
of any adjustments are needed.
The Ansible community package follows semantic versioning rules, so
incompatible changes are only made between major versions.
Unfortunately in this case, there are a number of major versions
between 2.9 and 5.0.
== User Experience ==
Users can remove the release collections and install separately
packaged collections or install from ansible-galaxy.
== Dependencies ==
Might need to conflict with some seperately packaged collections.
== Contingency Plan ==
* Contingency mechanism: Keep shipping ansible classic, but it will go
EOL and updates will become much harder.
* Contingency deadline: N/A (not a System Wide Change)
* Blocks release? N/A (not a System Wide Change)
== Documentation ==
N/A (not a System Wide Change)
== Release Notes ==
Ansible is now shipped as 'ansible-core' (the engine) and a curated
set of Ansible collections.
Users can use 'dnf install ansible' to install ansible-core as well as
the Ansible collections included in the upstream Ansible releases.
Users can also opt to 'dnf install ansible-core' and then install
collections manually from standalone packages or via ansible-galaxy.
--
Ben Cotton
He / Him / His
Fedora Program Manager
Red Hat
TZ=America/Indiana/Indianapolis
2 years, 7 months