Re: Loud PC speaker beep during reboot, sometimes

2022-09-22 Thread AV via test 
On Thu, 2022-09-22 at 10:41 +0200, Kamil Paral wrote:
> Completely randomly, my laptop sometimes emits a loud PC speaker beep
> while rebooting/powering off Fedora 37. The beep is very strong, and
> as a PC speaker sound, it of course ignores any configured volume
> level, mute status, and even headphones plugged in. I fortunately am
> in a different room than the rest of my family sleeps in, but if I
> were in the same room, and were I just a regular user, this would
> probably be the last day of Fedora on that laptop. The beep is that
> loud and uncomfortable, especially at night.
> 
> I wonder if somebody else running F37 noticed it as well? Any hints
> what might cause it and how we can fix it? It never happened on F36
> on the same laptop.

I experienced this 2 or 3 times (I think while installing fed 34 and
fed 35).
A very very loud screeching beep. I almost fell of my chair.
So I don't think it has anything specially to do with fed 37.
At the time I thought that something was wrong with the laptop or that
I had
done something not compatible with normal laptop use.
But as everything worked normally afterwards I forgot about it.
And I also forgot to lookup information about 'signals' related to
pc functioning.

Strange that you experience this randomly. Maybe fed 37 has activated
the pc speaker in a strange way
Stan demonstrates it can be turned off but unless this can be
demonstrated
to be a quirk of fed 37 I think I would like to know the cause.  .

AV
___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le...@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/test@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Loud PC speaker beep during reboot, sometimes

2022-09-22 Thread stan via test 
On Thu, 22 Sep 2022 10:41:18 +0200
Kamil Paral  wrote:

> Completely randomly, my laptop sometimes emits a loud PC speaker beep
> while rebooting/powering off Fedora 37. The beep is very strong, and
> as a PC speaker sound, it of course ignores any configured volume
> level, mute status, and even headphones plugged in. I fortunately am
> in a different room than the rest of my family sleeps in, but if I
> were in the same room, and were I just a regular user, this would
> probably be the last day of Fedora on that laptop. The beep is that
> loud and uncomfortable, especially at night.
> 
> I wonder if somebody else running F37 noticed it as well? Any hints
> what might cause it and how we can fix it? It never happened on F36
> on the same laptop.

alsa usually has the pc speaker disabled.  It has been a long time, but
I think there is a configuration option that can turn it on.  Is it
possible that you have somehow turned this on?

I found this in the arch linux documentation,

https://wiki.archlinux.org/title/PC_speaker

Globally

The PC speaker can be disabled by unloading the pcspkr kernel module:
Note: This will not disable your entire sound system, only the PC
speaker.

# rmmod pcspkr

Blacklisting the pcspkr module will prevent udev from loading it at
boot. Create the file:

/etc/modprobe.d/nobeep.conf

blacklist pcspkr

Blacklisting it on the kernel command line is yet another way. Simply
add modprobe.blacklist=pcspkr to your bootloader's kernel line. 


ALSA

For most sound cards the PC speaker is listed as an ALSA channel, named
either PC Speaker, PC Beep, or Beep. To mute the speaker, either use
alsamixer or amixer , for example:

$ amixer set 'PC Speaker' 0% mute

To unmute the channel, see Advanced Linux Sound Architecture#Unmuting
the channels. Tip: If you are using PulseAudio and the PC speaker
channel is not listed for the default ALSA device, try selecting the
device corresponding to the sound card - PulseAudio proxy controls may
not list the PC speaker.
___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le...@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/test@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: F37 Final blocker status update

2022-09-22 Thread Adam Williamson 
On Thu, 2022-09-22 at 13:01 -0400, Ben Cotton wrote:
> 
> 6. mesa — https://bugzilla.redhat.com/show_bug.cgi?id=2123274 — NEW
> totem: nouveau_pushbuf_data(): totem killed by SIGABRT
> 
> totem plays ~1 second of video and then crashes. This appears to
> happen with all video formats. This appears to be an issue in
> multithreading support in the nouveau driver, which is fixed upstream.
> The fix is large and may not be suitable for backporting, but would be
> available in a mesa-22.3 update.

Well, it's not so much backporting that's the problem. It's just that
it's a large change and nobody seems to be super confident about just
throwing it into F37, whether via a backport or a new mesa release. I'm
really not sure what we should do here. It may honestly be safer to
ship the way we are, with a known bug, and then do mesa as a post-
release update; it's much safer in a way to do something as a post-
release update, because then we at least have a "known not-completely-
broken" version in the release repo, and our release live image is in a
known-not-completely-broken state. We can then let the update sit for
testing until we're relatively confident it's better than the current
state.

If we decide to put the new version in for release then belatedly find
out the new code has significant problems that are worse than video
playback in totem, we're up a much rougher creek.

So, this one seems like a bit of a tough call. It would be a good idea,
I think, to get an update with the new code rolled at least, then
people can try it out and we can start getting an idea whether it has
problems...
-- 
Adam Williamson
Fedora QA
IRC: adamw | Twitter: adamw_ha
https://www.happyassassin.net

___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le...@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/test@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: F37 seems to require a reboot after updates of firmware packages in order for firefox to run.

2022-09-22 Thread stan via test 
On Fri, 19 Aug 2022 06:45:14 -0700
stan  wrote:

> On Fri, 19 Aug 2022 06:31:36 -0700
> stan  wrote:
> 
> New development.  I decided to run strace on the process to see if it
> would give any useful information.  And the program started!  That
> makes it look like there might be a race happening, with strace
> slowing things down enough that it didn't occur.
> 
> A workaround of sorts.  :-)

This became more common, and strace sometimes worked and sometimes not.
But what works every time is to start chromium, then close it.  After
that, nightly starts every time.  There must be a missing library or
setting that chromium sets up, and then firefox can use it.  I haven't
looked further.
___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le...@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/test@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: F37 Final blocker status update

2022-09-22 Thread Ben Cotton 
Action summary


Accepted blockers
-

1. anaconda — Custom partitioning with 2 drives selected, bootloader
fails to install due to one drive not having a BIOS Boot partition —
ON_QA
ACTION: QA to verify FEDORA-2022-c20d42f3bc

2. gnome-initial-setup — Unable to set up enterprise account with
gnome-initial-setup, clicking continue does not join the domain —
VERIFIED
ACTION: (none)

3. gnome-shell — GNOME Initial Setup uses the English keyboard,
instead of the default keyboard — VERIFIED
ACTION: (none)

4. greenboot — greenboot-grub2-set-counter.service fails on 38 IoT
with "cannot open `/boot/grub2/grubenv.new`: No such file or
directory." — NEW
ACTION: Maintainers to diagnose issue

5. grub2 — Windows with bitlocker enabled can't be booted, needs to
use bootnext instead of chainloader — NEW
ACTION: QA to finalize updated criterion proposal

6. mesa — totem: nouveau_pushbuf_data(): totem killed by SIGABRT — NEW
ACTION: Maintainers to update mesa with fixes for F37


Proposed blockers
-

1. abrt — Abrt does not report a segfault which is reported in
journalctl. — ASSIGNED
ACTION: Maintainers to diagnose issue

2. nautilus — Nautilus thumbnailing doesn't work on hidpi screens — NEW
ACTION: Upstream to diagnose issue


Bug-by-bug detail
=

Accepted blockers
-

1. anaconda — https://bugzilla.redhat.com/show_bug.cgi?id=2088113 — ON_QA
Custom partitioning with 2 drives selected, bootloader fails to
install due to one drive not having a BIOS Boot partition

When using custom partitioning on two drives with /boot on a RAID 1
device, the installer only creates one BIOS boot. grub2-install is run
against both drives, but the second fails because it has no BIOS boot
partition. FEDORA-2022-c20d42f3bc contains a candidate fix.

2. gnome-initial-setup —
https://bugzilla.redhat.com/show_bug.cgi?id=2123494 — VERIFIED
Unable to set up enterprise account with gnome-initial-setup, clicking
continue does not join the domain

Initially the buttons were missing. Update FEDORA-2022-50e585b456
fixed that issue, however clicking the button does not joing the
domain. Instead, the user is returned to the domain credentials
screen, resulting in an endless loop. gnome-initial-setup-43.0-3.fc37
contains a verified fix.

3. gnome-shell — https://bugzilla.redhat.com/show_bug.cgi?id=2121110 — ASSIGNED
GNOME Initial Setup uses the English keyboard, instead of the default keyboard

Regardless of the default keyboard setting, g-i-s uses the English
keyboard. Relatedly, new users have the English keyboard selected,
even though another language is shown as the default.
FEDORA-2022-b14944cb83 contains a verified fix.

4. greenboot — https://bugzilla.redhat.com/show_bug.cgi?id=2121944 — NEW
greenboot-grub2-set-counter.service fails on 38 IoT with "cannot open
`/boot/grub2/grubenv.new`: No such file or directory."

greenboot service fails on a file-not-found error. This also results
in rebase tests failing because of conflicts with the rebase triggered
by the greenboot failure.

5. grub2 — https://bugzilla.redhat.com/show_bug.cgi?id=2049849 — NEW
Windows with bitlocker enabled can't be booted, needs to use bootnext
instead of chainloader

Dual-booting recent Windows 10 system with TPM 2.0 fails because
bitlocker can't be unsealed by the TPM. This was waived to F37 under
the "difficult to fix" exception. A proposed change to the release
criteria may exclude this from blocker status.

6. mesa — https://bugzilla.redhat.com/show_bug.cgi?id=2123274 — NEW
totem: nouveau_pushbuf_data(): totem killed by SIGABRT

totem plays ~1 second of video and then crashes. This appears to
happen with all video formats. This appears to be an issue in
multithreading support in the nouveau driver, which is fixed upstream.
The fix is large and may not be suitable for backporting, but would be
available in a mesa-22.3 update.


Proposed blockers
-

1. abrt — https://bugzilla.redhat.com/show_bug.cgi?id=2128662 — ASSIGNED
Abrt does not report a segfault which is reported in journalctl.

In some circumstances (currently unclear), abrt does not report
segfaults. Restarting abrt-journal-core (including via reboot) causes
abrt to work correctly again.

2. nautilus — https://bugzilla.redhat.com/show_bug.cgi?id=2127618 — NEW
Nautilus thumbnailing doesn't work on hidpi screens

No thumbnails are generated in the file manager on hidpi screens.
Other functionality works. Reported upstream as
https://gitlab.gnome.org/GNOME/nautilus/-/issues/2487
-- 
Ben Cotton
He / Him / His
Fedora Program Manager
Red Hat
TZ=America/Indiana/Indianapolis
___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le...@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.fedora

Re: Heads up: GNOME 43.0 megaupdate is in testing

2022-09-22 Thread Kalev Lember 

On 9/21/22 18:02, Kamil Paral wrote:

Hi Kalev,
while it's not essential, I find it unfortunate that Night Light 
controls are now broken, I think many people use it:
https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/2056 

It should be fixed by this commit (I haven't tested it), but it seems 
it's not present in mutter-43.0-1:
https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2623 



Hi Kamil,

Sure, I went ahead and backported that to mutter-43.0-2.fc37:
https://bodhi.fedoraproject.org/updates/FEDORA-2022-c7746c91b6

Can you try if it makes it work?

--
Kalev
___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le...@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/test@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Loud PC speaker beep during reboot, sometimes

2022-09-22 Thread Sean Mottles 
I imagine this is the “pcspkr” kernel module which seems to be loaded by 
default (verified with the F37 Beta Workstation ISO in QEMU)

> 
> On Sep 22, 2022, at 10:42, Kamil Paral  wrote:
> 
> 
> Completely randomly, my laptop sometimes emits a loud PC speaker beep while 
> rebooting/powering off Fedora 37. The beep is very strong, and as a PC 
> speaker sound, it of course ignores any configured volume level, mute status, 
> and even headphones plugged in. I fortunately am in a different room than the 
> rest of my family sleeps in, but if I were in the same room, and were I just 
> a regular user, this would probably be the last day of Fedora on that laptop. 
> The beep is that loud and uncomfortable, especially at night.
> 
> I wonder if somebody else running F37 noticed it as well? Any hints what 
> might cause it and how we can fix it? It never happened on F36 on the same 
> laptop.
> 
> Thanks,
> Kamil
> 
> ___
> test mailing list -- test@lists.fedoraproject.org
> To unsubscribe send an email to test-le...@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/test@lists.fedoraproject.org
> Do not reply to spam, report it: 
> https://pagure.io/fedora-infrastructure/new_issue
___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le...@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/test@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Loud PC speaker beep during reboot, sometimes

2022-09-22 Thread Kamil Paral 
Completely randomly, my laptop sometimes emits a loud PC speaker beep while
rebooting/powering off Fedora 37. The beep is very strong, and as a PC
speaker sound, it of course ignores any configured volume level, mute
status, and even headphones plugged in. I fortunately am in a different
room than the rest of my family sleeps in, but if I were in the same room,
and were I just a regular user, this would probably be the last day of
Fedora on that laptop. The beep is that loud and uncomfortable, especially
at night.

I wonder if somebody else running F37 noticed it as well? Any hints what
might cause it and how we can fix it? It never happened on F36 on the same
laptop.

Thanks,
Kamil
___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le...@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/test@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue