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

Hide blueman-applet in KDE and GNOME #2549

Closed
wants to merge 1 commit into from

Conversation

mxaddict
Copy link

@mxaddict mxaddict commented Dec 9, 2024

New versions of GNOME and KDE have dedicated UI for this

Copy link

sonarqubecloud bot commented Dec 9, 2024

@infirit
Copy link
Contributor

infirit commented Dec 9, 2024

That's a no. Many people use blueman on plasma and GNOME.

@infirit infirit closed this Dec 9, 2024
@mxaddict
Copy link
Author

mxaddict commented Dec 9, 2024

I'm pretty sure if they are using blueman on KDE ang GNOME they are fully capable of starting the applet yes?

Would it not make more since to have this as opt-in rather than opt out?

Scenario:

  1. Have KDE/GNOME installed alongside a window manager
  2. Use blueman in window manager
  3. Want to use Default KDE/GNOME UI for bluetooth
  4. User has to disable blueman via /etc/xdg config

As a side note nm-applet already has this option set to make it opt in.

@cschramm
Copy link
Member

cschramm commented Dec 9, 2024

New versions of GNOME and KDE have dedicated UI for this

For configuring autostart? Please elaborate. In #2102 we concluded that current Gnome does not have any proper mechanism for that anymore (at that time). That discussion was exactly around users switching between Gnome and another desktop and preferring Gnome Bluetooth in Gnome. We did not find a proper solution. The best idea was to implement our own autostart switch (creating and removing a link) and leave it to the user to somehow set things up for the desktops he wants to use blueman with. Not sure if that's actually any better than requiring him to override the autostart with his preferences.

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 this pull request may close these issues.

3 participants