I’m currently expiriencing issues with fedora and VLC and my bluetooth connections to other devices. So now I can’t really pin point the issue as this happens sometimes and works well on other occasions but it is really annoying because it crashed on me after a long day of work. So now the issue is that sometimes the bluetooth device connects and fedora recognizes that it is a sound output device (headphones) it then selects it as the primary output audio device but as this happens audio output doesn’t work on VLC it crashes all sound and it doesn’t sound. Sometimes it happens on youtube too and I kinda have to move the video forward a bit for it to work. it’s really confusing me and I don’t know how I’m supposed to debug this. Maybe if someone had any ideas they could share cos I could use some help with this.
The problem you’re describing isn’t very clear. May help to clarify.
But in the meantime, if you’re having some kind of bluetooth issue with VLC, what I’d check is:
Run VLC from terminal, so you will see the application logs on the terminal in real time as you reproduce the issue.
Check the journal log for any bluetooth issues right after you reproduce the issue. E.g. journalctl --since "5 minutes ago"
Nice Yuri, thanks a lot for this. You’re right for me not being clear about the issue and I will drop a new post clarifying everything to my best ability I will also provide logs and steps to reproduce. I didn’t even know journalctl existed till now haa let me run that and try pin pointing the issue.
But could it be a driver issue ? Because I can’t even see the device information and even the battery percentage of the connected headphones and last time I checked I remember the gnome-control-panel had this implemented.
It’s possible. Your laptop model might have an Intel or Realtek Wifi/Bluetooth adapter. Intel is generally considered more reliable, so if you have the latter, that could explain the issues.
You can check which wireless adapter you have with lspci -v and lsusb.
The driver comes with the kernel so you shouldn’t need to update anything aside from updating the kernel to get the latest driver.
More detail that may help us understand your issue can be provided by installing inxi, running inxi -ezxx in a terminal, and posting the output as web-discoverable pre-formatted text (use the </> button). The journal collects massive details that are useful for understanding issues, but some effort is needed to filter out irrelevant details. See: https://docs.fedoraproject.org/en-US/quick-docs/viewing-logs/.
haa let me run that and try pin pointing the issue.