FS#74697 - [gnome-control-center] issue with Bluetooth name

Attached to Project: Arch Linux
Opened by mattia (nTia89) - Tuesday, 10 May 2022, 17:00 GMT
Last edited by Toolybird (Toolybird) - Tuesday, 30 August 2022, 06:20 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To No-one
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

Description:

Bluetooth broadcast name is "wrong".

I opened a bug report in the GNOME's official bug tracker but it has been closed since according with them, it is a *fault of us*.
Exact answer here[https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/1786#note_1448321].

Please refer to the original issue, well written and with screenshots.


Additional info:
* upstream bug [https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/1786]
This task depends upon

Closed by  Toolybird (Toolybird)
Tuesday, 30 August 2022, 06:20 GMT
Reason for closing:  Not a bug
Comment by Toolybird (Toolybird) - Tuesday, 26 July 2022, 07:41 GMT
Our bluetoothd is correct AFAICT. Can't you just do what is suggested in the upstream report and set your "pretty" hostname [1] via hostnamectl [2] ? Please let us know.

[1] https://man.archlinux.org/man/org.freedesktop.hostname1.5.en#RECOMMENDATIONS
[2] https://man.archlinux.org/man/core/systemd/hostnamectl.1.en#COMMANDS
Comment by mattia (nTia89) - Friday, 26 August 2022, 21:05 GMT
  • Field changed: Percent Complete (100% → 0%)
Sorry for the missed answer; the issue is still valid and changing the name via `hostnamectl` don't work
Comment by Toolybird (Toolybird) - Friday, 26 August 2022, 21:07 GMT
Please show:
1. the exact command you used to set the "pretty" hostname
2. the output of `cat /etc/machine-info'
Comment by mattia (nTia89) - Saturday, 27 August 2022, 14:33 GMT
1. hostnamectl hostname "arch-xps"
2. $ cat /etc/machine-info
ICON_NAME=computer-laptop
CHASSIS=laptop
DEPLOYMENT=production
Comment by Toolybird (Toolybird) - Saturday, 27 August 2022, 23:41 GMT
Could you please try just changing the "pretty" hostname as per the doc links above?

$ hostnamectl hostname mattia-xps --pretty

$ hostnamectl | grep Pretty

/etc/machine-info should now contain an entry "PRETTY_HOSTNAME=mattia-xps"

Then maybe reboot and see if it works?
Comment by mattia (nTia89) - Sunday, 28 August 2022, 07:15 GMT
I have done as you suggested; now I have that PRETTY entry but issue is still here...

$ cat /etc/machine-info
ICON_NAME=computer-laptop
CHASSIS=laptop
DEPLOYMENT=production
PRETTY_HOSTNAME=mattia-xps

PS: my previous command `hostnamectl hostname "arch-xps"` should have changed the PRETTY name too; in fact, following the `hostnamectl` man page[2]: "(...)If an optional argument NAME is provided then the command changes the system hostname to NAME. By default, this will alter the pretty, the static, and the transient hostname alike;(...)"
Comment by Toolybird (Toolybird) - Sunday, 28 August 2022, 22:33 GMT
Ok, so maybe we're barking up the wrong tree. Found some more stuff online which suggests a Chromium based browser is somehow playing a role. This thread is from the same upstream dev who closed your report [1]. Here's an old reddit thread [2]. Here's something else to try [3].

Either way, it's looking like no actionable Arch bug here. You'll have to examine your system in detail to find the reference to "ChromeLinux_D56B" and edit it.

[1] https://www.spinics.net/lists/linux-bluetooth/msg68997.html
[2] https://old.reddit.com/r/linux/comments/4j2g13/everytime_i_launch_chrome_it_renames_my_bluetooth/
[3] https://askubuntu.com/questions/830550/why-does-my-linux-appear-as-chromelinux-c4ea-on-my-windows-10-laptop
Comment by mattia (nTia89) - Monday, 29 August 2022, 14:57 GMT
Ok, wait one second... Chroming?! things get complicated

First step: is it confirmed as a bug?
Do you have this issue too, or I am the only one?
Comment by Toolybird (Toolybird) - Tuesday, 30 August 2022, 06:20 GMT
I think you're the only one. If it was a chromium bug it was apparently fixed long ago (according to the posted links). If there is leftover bogus config on your system, you'll need to find it.

Loading...