Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Rapid dis- and reappearing of the blueman applet icon #2311

Open
franzmondlichtmann opened this issue Apr 1, 2024 · 15 comments · Fixed by #2334
Open

Rapid dis- and reappearing of the blueman applet icon #2311

franzmondlichtmann opened this issue Apr 1, 2024 · 15 comments · Fixed by #2334

Comments

@franzmondlichtmann
Copy link

franzmondlichtmann commented Apr 1, 2024

blueman: 2.3.5
BlueZ: 5.71
Distribution: OpenSuse Tumbleweed (Rolling Release)
Desktop environment: i3

Blueman is running, but the bluetooth-applet-icon is "appearing" and disappearing (in very short spans of time ca. every ~30 milliseconds) in the right part of the bar. The Icon itself is not visible but a black or transparent square where the icon should be.
I tried it out with blueman running and with other programs closed.
The bug seems to appear when I start the dolphin file manager.
This right part of the bar is part of the desktop environment i3 (if I understood correctly).
I already filed a bug in the bumblebee-status bar github page, but they say it's very probably not their bug.
I tried it with bumblebee-status and i3 default status bar, but the bug happens with both statusbars, and seems independent of the set status bar. I don't think its a graphical glitch in the sense, that it has anything to do with the gpu.
Maybe it's the way the icon gets drawn or updated?

State 1:
image
State 2:
image
Imagine rapid switching between the two states.

In the next test, I closed the other applet icons, so that only blueman is open. Same problem.

@franzmondlichtmann
Copy link
Author

franzmondlichtmann commented Apr 1, 2024

If I disable the status-notifier-item plugin in blueman the blueman icon appears and no more rapid dis- and reappearing of the "transparent or black" box.

@cschramm
Copy link
Member

cschramm commented Apr 1, 2024

Anything to possibly isolate it? Cannot reproduce with blueman 2.3.5, i3 4.23, i3status 2,14.

@franzmondlichtmann
Copy link
Author

franzmondlichtmann commented Apr 2, 2024

It happens on my pc every time when I get this message box from dolphin.
"What do you wish to do with this file? Execute. Cancel."
image

@cschramm
Copy link
Member

cschramm commented Apr 2, 2024

Pardon my ignorance, but how can I trigger that?

@franzmondlichtmann
Copy link
Author

franzmondlichtmann commented Apr 2, 2024

You need some executable program (for example anki). But a executable script should also do it. Right click on the script -> properties -> make executable -> execute with double click in dolphin.
The error happens when the message box opens.

@cschramm
Copy link
Member

cschramm commented Apr 2, 2024

Ok, I managed to get that dialog, using an executable shell script (i.e. a text file with a shebang). It looks completely different though, regarding both styling and content (I get an additional "Open" button). Does not cause any problem with the tray icon. Dolphin 23.08.5.

@franzmondlichtmann
Copy link
Author

I uninstalled many packages, including plasma 6 desktop environment and many other KDE 6 packages, therefore the issue does not happen anymore. This is kind of a shame, because I would have liked to know how this issue happens.
Now I'm torn apart, if I should install plasma again or not.

@franzmondlichtmann
Copy link
Author

franzmondlichtmann commented Apr 2, 2024

The styling is coming from qt6ct, a app which lets you change look and feel of qt6 programs in i3 and similar window managers.

@franzmondlichtmann
Copy link
Author

franzmondlichtmann commented Apr 2, 2024

Ok I reinstalled Plasma 6 Desktop Environment along with it's dependencies. And Dolphin as a "standalone" application does not trigger the bug, but with Plasma 6 and it's dependencies installed the bug happens!
And to clarify, the bug happens with Plasma 6 installed, while using i3.

@infirit
Copy link
Contributor

infirit commented Apr 2, 2024

Make sure bluedevil is not installed by using --assume-installed=bluedevil when installing plasma.

@franzmondlichtmann
Copy link
Author

I won't install any KDE applications anymore, because uninstalling and installing KDE Plasma again, broke my system. So I might make a test in a VM, but later.

@cschramm
Copy link
Member

cschramm commented Apr 5, 2024

Shot in the dark: Do you happen to have audio profiles or recent connection items with & in their name? #2327 could be a fix then. While working on it I found that it's not only causing warnings as in #2326, but it can e.g. cause #2289 in Cinnamon. One obvious way the KDE packages could trigger it could be that they connect an audio device which leads to the profiles getting added to the menu.

@cyberpunkrocker-zero
Copy link

cyberpunkrocker-zero commented Apr 7, 2024

That on-off flashing started on Arch Linux after the update to Plasma6, with both 2.3.5 and 2.4 versions of blueman. When starting blueman-applet from terminal, I get the following messages:

blueman-applet 20.33.34 WARNING  PluginManager:150 __load_plugin: Not loading PPPSupport because its conflict has higher priority
blueman-applet 20.33.34 WARNING  PluginManager:150 __load_plugin: Not loading DhcpClient because its conflict has higher priority

@cyberpunkrocker-zero
Copy link

As noted above, either disabling the status-notifier-item plugin on blueman, or removing KDE6's Bluedevil helps.

cschramm added a commit to cschramm/blueman that referenced this issue Apr 7, 2024
kded6 provides an `org.kde.StatusNotifierWatcher` service without its usual `/StatusNotifierWatcher` object if Plasma Workspace's StatusNotifierWatcher module is registered but not loaded (https://invent.kde.org/plasma/plasma-workspace/-/merge_requests/3301). We thus cannot just assume the whole service to be unavailable if the registration fails as we restart the tray application when the name appears.

This is a problem if the Plasma Workspace is around especially on i3 where no other application registers `org.kde.StatusNotifierWatcher`.

Closes blueman-project#2311
@cschramm cschramm linked a pull request Apr 7, 2024 that will close this issue
@cschramm
Copy link
Member

cschramm commented Apr 7, 2024

I was able to reproduce it now, simply by running kded6 on i3, but cannot confirm that removing bluedevil helps. #2334 should fix it.

cschramm added a commit that referenced this issue Apr 7, 2024
kded6 provides an `org.kde.StatusNotifierWatcher` service without its usual `/StatusNotifierWatcher` object if Plasma Workspace's StatusNotifierWatcher module is registered but not loaded (https://invent.kde.org/plasma/plasma-workspace/-/merge_requests/3301). We thus cannot just assume the whole service to be unavailable if the registration fails as we restart the tray application when the name appears.

This is a problem if the Plasma Workspace is around especially on i3 where no other application registers `org.kde.StatusNotifierWatcher`.

Closes #2311
infirit pushed a commit to infirit/blueman that referenced this issue Apr 8, 2024
kded6 provides an `org.kde.StatusNotifierWatcher` service without its usual `/StatusNotifierWatcher` object if Plasma Workspace's StatusNotifierWatcher module is registered but not loaded (https://invent.kde.org/plasma/plasma-workspace/-/merge_requests/3301). We thus cannot just assume the whole service to be unavailable if the registration fails as we restart the tray application when the name appears.

This is a problem if the Plasma Workspace is around especially on i3 where no other application registers `org.kde.StatusNotifierWatcher`.

Closes blueman-project#2311
infirit pushed a commit to infirit/blueman that referenced this issue May 15, 2024
kded6 provides an `org.kde.StatusNotifierWatcher` service without its usual `/StatusNotifierWatcher` object if Plasma Workspace's StatusNotifierWatcher module is registered but not loaded (https://invent.kde.org/plasma/plasma-workspace/-/merge_requests/3301). We thus cannot just assume the whole service to be unavailable if the registration fails as we restart the tray application when the name appears.

This is a problem if the Plasma Workspace is around especially on i3 where no other application registers `org.kde.StatusNotifierWatcher`.

Closes blueman-project#2311
infirit pushed a commit to infirit/blueman that referenced this issue May 17, 2024
kded6 provides an `org.kde.StatusNotifierWatcher` service without its usual `/StatusNotifierWatcher` object if Plasma Workspace's StatusNotifierWatcher module is registered but not loaded (https://invent.kde.org/plasma/plasma-workspace/-/merge_requests/3301). We thus cannot just assume the whole service to be unavailable if the registration fails as we restart the tray application when the name appears.

This is a problem if the Plasma Workspace is around especially on i3 where no other application registers `org.kde.StatusNotifierWatcher`.

Closes blueman-project#2311
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants