this post was submitted on 25 Jul 2023
4 points (100.0% liked)

Linux Troubleshooting and scripts

468 readers
1 users here now

this is a community for sharing your scripts that help when working with Linux as well a general troubleshooting.

Rules

Feel free to ask any kind of support questions, as we grow more succinct answers will be available. Let's make this community grow.

We are important to one another, not only in the linux world but also in the fediverse as a whole. Feel free to reach out to me with questions or concerns, as we grow bigger I will look into adding mods. (This section will be updated as needed.)

founded 1 year ago
MODERATORS
 

Hi, I am new to linux and started off with Nobara KDE, updated to latest and facing a problem with my new bluetooth keyboard. It can store upto 3 devices and can switch between them. Whenever I switch out of the system to my work laptop it force mutes all playback device without interfering with media and I have to toggle it back on manually. I have pulse audio and but I believe only pipewire-pulse is running under process. I am adding some screen shots with imgur hoping that would help. Would appreciate some help or hints on how this cant be fixed. Thanks.

you are viewing a single comment's thread
view the rest of the comments
[–] Efwis 2 points 1 year ago* (last edited 1 year ago) (1 children)

i realize the main point of nobara is to stay away from the terminal, however what would really help is if you install inxi, disable the script you created reboot the system so the script is cleared from memory. Let the issue happen again and then enter this on your teminal

sudo inxi -Fxzz

sudo journlctl -S 1h

posting the info into your next reply

[–] RogueBanana 1 points 1 year ago (1 children)

Sorry this completely slipped my mind. I have ran the commands but truncated the log with the only bluetooth relevant info. Let me know if the whole log is needed. Thanks.

Link to pastebin: https://pastebin.com/gDUtZgbY

[–] Efwis 2 points 1 year ago

Ok, it seems this looks like a coding bug in powerdevil, which is a KDE issue.

At this point I would recommend posting a bug report at https://bugs.kde.org/