Bug 2173464

Summary: Whole system crashes when using the seekbar in YouTube
Product: [Fedora] Fedora Reporter: Actias <b.okj0q>
Component: systemdAssignee: systemd-maint
Status: CLOSED INSUFFICIENT_DATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 37CC: fedoraproject, filbranden, lnykryn, msekleta, ryncsn, systemd-maint, yuwatana, zbyszek
Target Milestone: ---Keywords: Reopened
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-08-09 10:59:45 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
journalctl boot unit bluetooth.txt
none
journalctl --boot --priority=err
none
dmesg | grep -i error none

Description Actias 2023-02-26 23:54:52 UTC 
Description of problem:
When using Firefox to play a YouTube video, using the seek bar can crash the whole system. 

Version-Release number of selected component (if applicable):
systemd-251.11-2.fc37.x86_64, but I have idea if this is an actual systemd issue

How reproducible:
Occasionally

Steps to Reproduce:
1. Use a bluetooth headset
2. Play a video in YouTube using Firefox (firefox-110.0-3.fc37.x86_64)
3. Use the seek bar to go to another part of the video. Keep doing this repeatedly


Actual results:
The screen will turn full black at some point. It won't even possible to switch to another tty.

Expected results:
N/A

Additional info:
System crashed in 20:26
Comment 1 Actias 2023-02-26 23:55:26 UTC 
Created attachment 1946644 [details]
journalctl boot unit bluetooth.txt
Comment 2 Actias 2023-02-26 23:56:09 UTC 
Created attachment 1946645 [details]
journalctl --boot --priority=err
Comment 3 Actias 2023-02-27 00:04:02 UTC 
Created attachment 1946646 [details]
dmesg | grep -i error
Comment 4 Zbigniew Jędrzejewski-Szmek 2023-02-27 08:13:39 UTC 
*** Bug 2173463 has been marked as a duplicate of this bug. ***
Comment 5 Zbigniew Jędrzejewski-Szmek 2023-02-27 08:15:35 UTC 
Just attach a full log. The information provided now is useless.
Also, provide the kernel version and information about the hardware.
Comment 6 Actias 2023-02-28 01:33:53 UTC 
Kernel: 6.1.13-200.fc37.x86_64

HW info:
- Device model: Dell Inspiron 3583
- Memory: 16GB
- GPU: Intel UHD Graphics 620 (WHL GT2)
- Processor: Intel i5-8265U
Comment 7 Zbigniew Jędrzejewski-Szmek 2023-03-06 08:45:12 UTC 
As mentioned, we can't do much without full logs. This looks like a hardware/driver
issue, but it's hard to say anything based on a few lines of unrelated output.

If the issue occurs again, please at least attach output of 'journalctl -b' or 'journalctl -b-1'.
Comment 8 Actias 2023-03-06 11:27:47 UTC 
(In reply to Zbigniew Jędrzejewski-Szmek from comment #7)
> As mentioned, we can't do much without full logs. This looks like a
> hardware/driver
> issue, but it's hard to say anything based on a few lines of unrelated
> output.
> 
> If the issue occurs again, please at least attach output of 'journalctl -b'
> or 'journalctl -b-1'.

I will attach a new log as soon as possible! Thanks! 

Also, when I do this, should I reopen this issue?
Comment 9 Zbigniew Jędrzejewski-Szmek 2023-03-06 11:37:55 UTC 
I'm not sure if you can reopen it, so I did it now.