Some programmers has done their best to fix all sound issues which were
typical for some integrated sound chips on laptops.
Skype perfectly work with The microphone even if user uses wired headset
connected to The input output one connector in this audio subsystem.
Previously it have been necessary to shut down The laptop, connect
analog wired headset with The microphone or even ordinary analog head
phones to The connector and start Fedora or also other Linux distributions.
If user have connected The device to The connector when The system have
been allready booted, sound output have not been directed to The device.
Only build in amplifier has worked.
Now, it is allready The past.
I must compare this new feature with Ubuntu. If Ubuntu still lack this
feature, Redhad elite developers were The first one, who has solved this
Very well done.
Unfortunately, sound quality while making Skype calls related to
microphone controll can not be compared with Android or with Windows.
But it is problem of non standardized Linux distros and various versions
of Pulseaudio and kernel device drivers.
May be, that once a pone time, also microphone support in Skype will be
It would be necessary to enable 20 DB auto boost and suppress The
possible back feetback if hardware do not automatically eliminate it.
Today I updated the software on my Fedora 36 and now there is no sound.
I used Gnome Software to update. Neither VLC nor Firefox produces
sound. In Settings -> Sound -> Output there are two values under Output
Device, both saying HDMI/DisplayPort - Built-in Audio. No difference
between them, when using the Test functionality both stay silent.
It seems that Win10 guest VMs are now choking after Microsoft did …something
to reject the current OVMF firmware.
This entire discussion, pretty much, is way over my head:
As best as I can make things out:
There is an alternative OVMF firware called "4M" firmware that works.
The edk2-ovmf package contains files named OVMF_CODE.secboot.fd and
OVMF_VARS.secboot.fd which are blacklisted by Microsoft.
Debian and other distributions apparently ship "OVMF_CODE_4M" and
"OVMF_VARS_4M" firmware which is still good. People have reported success
extracting those images and repointing their qemu VM configuration to them.
I don't grasp the underlying issue well enough to be able to file something
intelligent in Bugzilla, in order to update Fedora packaging. I'm hoping
that someone else here has enough domain knowledge to create a bug that
points the ed2k packagers in the right direction. I tried looking at the
SRPM, and I did not see anything in there that I could understand.
What's the deal with maintaining mailing lists on Fedora these days?
For years I've used mailman (first mailman2, now mailman3) on Fedora to
administer mailing lists. In mailman3, you also need postorius to
provide a web interface to users and hyperkitty to provide mail archive
On Fedora 35, mailman2 isn't available anymore, so that's when I
switched to mailman3. The original Fedora 35 did not have postorius,
but that became available later. Hyperkitty on the other hand is not
available on fedora 35. I use an rpm that I built myself.
On Fedora 36, mailman3 can be installed, but both postorius and
hyperkitty (there it is in the repository) cannot. They both depend on
a too old version of django.
On Fedora 37 (I know, not released yet, so any complaints should go to
the testing list) none of the packages can be installed since they all
depend on python 3.10 and F37 will come with 3.11. The packages are
actually the unmodified F36 packages.
Do people use mailman3 on Fedora? If so, how?
Should I invest time in getting it to work in a python virtual
environment? And how would that work with SELinux?
This very mailing list (users(a)lists.fedoraproject.org) is managed with
mailman3, but does the system on which it runs run Fedora?
Dear elite developers, dear users in this mailing list,
Please, who of us know, if it would be possible to extend sound
devices support so wired headsets with The integrated buttons on The
microphone would be supported by not only Fedora distribution?
My dream is, that those wired headsets with buttons on The microphne
could be used as A alternate media controlling system on Mate desktop
But I do not know, if Alsa, Pulseaudio and The similar sound subsystems
support this technology. Or if it is impossible to implement at all?
I know, that The majority of users are using bluetooth devices. But
wired headsets have also its advantages.
Sure, if kernel device drivers would had to be reprogrammed from
scratch, I Am aware, that nobody will invest such plenty of time to
support wired headsets and their media controlling integrated buttons.
Mate can not grab such media keys as A keyboard code, so I can not
simply assign those media codes myself.
I Am very sorry for this non standard question.
With The deepest appreciation to all members of this mailing list.
Mgr. Janusz Chmiel
I would like to know, if enabling encryption of Fedora installation
in Anaconda installer will dramatically short The life cycle of SSD disk
or USB flash drives or SSD memory cart?
By other words. Does enabling encryption enforces much more write
requests on file system when comparing with not encrypted partitions?
Thank all engaged Fedora kernel developers for encryption kernel module.
Fedora 35, not fully up-to-date
I run a SiliconDust tuner that converts OTA TV to mp2, which I'm then
able to play back using mplayer. An hard-wired ethernet connection is
used between the tuner and the main CPU.
I notice that there are leftover kworker processes. They are mostly idle
and only a few have non-zero time, and then at most only a couple of
87547 ? I 0:00 [kworker/u16:1-phy0]
87554 ? I 0:00 [kworker/7:2-events]
87555 ? I 0:00 [kworker/5:2-events]
87556 ? I 0:00 [kworker/u16:2-btrfs-endio-write]
87557 ? I 0:00 [kworker/u16:3-btrfs-delalloc]
87558 ? I 0:00 [kworker/u16:5-btrfs-endio-write]
87559 ? I 0:00 [kworker/u16:7-events_unbound]
87560 ? I 0:00 [kworker/u16:9-btrfs-freespace-write]
87561 ? I 0:00 [kworker/u16:10]
87626 ? I< 0:00 [kworker/u17:1]
The leftover processes seem to vanish when the system is suspended.
Should I be concerned? In particular, I was not aware that I had
installed the btrfs filesystem.
I have recently started using the ethernet instead of wifi. I have not disabled the wifi, but I leave the ethernet cable inserted. Recently, I noticed that I was unable to start the computer. I thought it was a faulty F37 testing kernel, so I tried the previous kernel. Same thing. For some reason, I thought the only thing different is that I now have the ethernet hooked up, so I pulled the plug and tried to boot. Everything went fine.
How come I cannot boot the computer with the ethernet cable plugged in?
I've come across a circa 2011 Mac Book Pro. It appears to be in decent
condition save for the power adapter which appears to have been chewed by a
pet, so it doesn't flame on.
Has anyone had success installing fedora on one of these? Just curious
before I put money into a power adapter, I'm guessing someone ran the
battery flat (its probably shot anyway) and didn't pursue getting a new