-
Notifications
You must be signed in to change notification settings - Fork 0
Troubleshooting
issue tab
, whether the same bug had already been reported or not
Its time savier for me and you. If you are not satisfied with the answer given there, Just post/ask on the same report thread
whatever its in closed or open state.
Its mostly like Your system is not updated with the official repo, or not synced with mirrors for days.
This type of issue already had been reported. see here.
Step 1 : first check your PipeWire server is working
pactl info | grep "^Server"
Step 2 :-
a) Then check whether there is any error or warning on running PW services.
systemctl --user status pipewire{,-pulse}.{socket,service} pipewire-media-session.service
b) If there is any error or warning, restart whole pipwire Services.
systemctl --user restart pipewire{,-pulse}.{socket,service} pipewire-media-session.service
c) If solved stop here.
Step 3 :-
a) If not solved, check whether there is any error or warning on bluetooth.service
systemctl status bluetooth.service
b) If there is any error on bluetooth.service
restart it.
systemctl restart bluetooth.service
c) If solved stop here.
d) Otherwise go to step 2
If any weblinks/References through out this wiki has been broken, then search that weblinks/References
on wayback machine
- 🏠 Home
- ⚙️ Compiling
- 📃 Describing Project Tree
- 🔥 Creating Repo
- 🐧 All about GPG
- 💡 Multiple SSH Keys Tricks
- 🛠️ Troubleshooting