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

AudioProfiles's item isn't a sub-menu on auto-connection #2383

Closed
1 task done
kuraga opened this issue May 22, 2024 · 8 comments
Closed
1 task done

AudioProfiles's item isn't a sub-menu on auto-connection #2383

kuraga opened this issue May 22, 2024 · 8 comments
Labels

Comments

@kuraga
Copy link
Contributor

kuraga commented May 22, 2024

blueman: 2.4.1
BlueZ: 5.75
Distribution: Calculate Linux (Gentoo-based)
Desktop environment: XFCE 4.18

In most cases,
on auto-connection initiated by headphones (#1709 (comment)),
the sub-menu-item by AudioProfiles (applet) plugin
is just a menu-item (i.e. it isn't a sub-menu).
It's exactly not-sub-menu. It's not an empty sub-menu.

Interesting, there is the sub-menu in the manager window, at the same moment.

I don't think it's a serious issue but probably this observation could help in other cases.

@kuraga
Copy link
Contributor Author

kuraga commented May 22, 2024

On my observation, items here is legal, i.e. the standard list of sub-items-data.

@cschramm
Copy link
Member

You see an Audio Profiles for ... item without a sub menu and that's 100 % reproducible when the device initiates the connection but 0 % when you do from the system that's running blueman? You see sub menu items getting generated in the script, though?

Does restarting blueman-tray fix it (killall blueman-tray, then run it manually)?

Please provide dbus-send --print-reply --dest=org.blueman.Applet /org/blueman/Applet org.blueman.Applet.GetMenu and blueman-tray --loglevel debug (with no blueman-tray process running).

@kuraga
Copy link
Contributor Author

kuraga commented May 23, 2024

You see an Audio Profiles for ... item without a sub menu and that's 100 % reproducible when the device initiates the connection but 0 % when you do from the system that's running blueman?

Well, 80-90%.

You see sub menu items getting generated in the script, though?

Yes.

Does restarting blueman-tray fix it (killall blueman-tray, then run it manually)?

No.

Please provide dbus-send --print-reply --dest=org.blueman.Applet /org/blueman/Applet org.blueman.Applet.GetMenu

(at the moment of the described situation - i.e. item instead of item-with-sub-menu)
https://gist.github.com/kuraga/0ae5bb9d2018666108aa0514ec04d370

and blueman-tray --loglevel debug (with no blueman-tray process running).

$ blueman-tray --loglevel=DEBUG
(blueman-tray:28259): dbind-WARNING **: 18:50:44.592: Couldn't connect to accessibility bus: Failed to connect to socket /root/.cache/at-spi/bus_0: Отказано в доступе
blueman-tray 18.50.44 DEBUG    Tray:36 _on_name_appeared: Applet started on name org.blueman.Applet, showing indicator
blueman-tray 18.50.44 INFO     Tray:46 _on_name_appeared: Using indicator "StatusNotifierItem"

(no output on auto-connection)

@cschramm
Copy link
Member

So blueman-applet provides a proper sub menu to blueman-tray and blueman-tray uses the StatusNotifierItem implementation. Any data from the tray, e.g. with xfce4-panel --restart?

@kuraga
Copy link
Contributor Author

kuraga commented May 24, 2024

Now caught some different case, no menu item at all:

image

And xfce4-panel --restart helped!

image

@kuraga
Copy link
Contributor Author

kuraga commented May 24, 2024

Is it a race condition?.. The callback doesn't try to convert to a sub-menu since something around isn't ready yet...

@kuraga
Copy link
Contributor Author

kuraga commented May 26, 2024

BTW, on auto-connection, the item appears twice. And it doesn't have the sub-menu on the second time.

Also now I see the issue rarely. Don't know what has been changed (UPD: because I restarted blueman-tray?).

Copy link

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@github-actions github-actions bot added the stale label Jul 27, 2024
@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Aug 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants