| Summary: | New device connection attempt notification sometimes does not have a button to allow the connection | ||
|---|---|---|---|
| Product: | [Unmaintained] Bluedevil | Reporter: | Ahmed <ahmed.com> |
| Component: | general | Assignee: | David Rosca <nowrep> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | normal | CC: | justin.zobel, kde, kde, milanfix, nate, nicolas.fella, plasma-bugs-null |
| Priority: | HI | ||
| Version First Reported In: | 5.20.3 | ||
| Target Milestone: | --- | ||
| Platform: | Neon | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
| Attachments: |
Screenshot
dmesg_output Cinnamon_message |
||
|
Description
Ahmed
2020-11-08 09:46:02 UTC
Thanks for the report Ahmed, can you please provide a screenshot of what you are being shown when the controller is requesting access. Created attachment 133135 [details]
Screenshot
Thanks for the info. Created attachment 133136 [details]
dmesg_output
Here is a log of dmesg output. There are a few errors related to Bluetooth, and USB.
Seems like the notification should have a button on it or something. What happens on Cinnamon instead? Created attachment 133181 [details]
Cinnamon_message
I get a message like the one in the picture, and on Kubuntu, I get the same message that I get on KDE neon, but with buttons.
Thanks. Looks an issue with the bluetooth connection request notification somehow. this is odd, judging by the code (https://invent.kde.org/plasma/bluedevil/-/blob/master/src/kded/helpers/requestauthorization.cpp#L31) there should be actions to allow/deny the request. I don't have a PS3 controller at hand to test it myself though If I remember correctly, I was able to authorize the controller before on KDE neon User Edition, and I was able to use the controller one time, but all I get now is the message box without the buttons whatever how many times I try. How can I delete all Bluedevil configurations and all previous information about authorized devices? I do not know if that can help or not, but it is worth a shot. Somehow the buttons appeared when I was on a Wayland session, and I can now connect my wireless controller without any issues. I still use KDE Plasma 5.20.2. I have not updated it yet to 5.20.3. The same issue happens on KDE Plasma 5.20.3. The buttons only appears after logging in to a Wayland session. When I log in to Wayland, the buttons appear correctly, and after I log out from Wayland, and log in to Xorg, the buttons still appear correctly, but after I restart my machine, and log in to Xorg, the buttons disappear again. I would settle with using Wayland all the time, but it has a few issues that make it unbearable right now. Now, the opposite is happening. I can get the buttons to appear on Xorg, but not on Wayland. This issue does not make any sense. OK, I got it now. What fixes the issue is logging off, and logging in again. It does not matter if it is a wayland, or Xorg session, but I need to log in with the controller connected through USB cable. very odd. I'll see if I can get hands on a device to try to reproduce this I do not encounter this issue on Kubuntu 20.04, or Kubuntu 20.10. However, I have a similar issue on Kubuntu 20.10 when I try to pair a phone, or send files from a phone to KDE Plasma. Here is a link to this issue: https://bugs.kde.org/show_bug.cgi?id=429979 *** Bug 429979 has been marked as a duplicate of this bug. *** I'm starting to think you might have a general issue with action buttons in notification since I don't see bluedevil doing anything wrong I also have a PS3 controller and didn't notice this particular issue with the authorize/deny buttons. And I did reconnect the controller and paired many times because I found this other issue unrelated to this: https://bugs.kde.org/show_bug.cgi?id=432715 My system: Distro: OpenSUSE Tumbleweed KDE Plasma Version: 5.20.3 KDE Frameworks Version: 5.80.0 I notice that you have KDE 5.20.2 with KDE Framework 5.75.0, perhaps this issue comes from the recent KDE plasma paired with an old KDE Framework? *** Bug 440252 has been marked as a duplicate of this bug. *** For people experiencing this, can you rproduce it on Wayland? Or only on X11 *** This bug has been marked as a duplicate of bug 449196 *** (In reply to Nate Graham from comment #21) > For people experiencing this, can you rproduce it on Wayland? Or only on X11 > > *** This bug has been marked as a duplicate of bug 449196 *** It mostly happens with X11. I have to sign out and login in again using Wayland. |