Hey,
Using bluez 5.43 on Fedora 25, I get:
$ hciconfig hci0 name | grep Name
Name: 'ChromeLinux_900A'
When the PrettyHostname is:
$ grep PRETTY /etc/machine-info
PRETTY_HOSTNAME=classic
I grepped through a bunch of things, including the firmware, the kernel
sources, and bluez, but couldn't find the source of this name.
I'm also fairly certain that the hostname plugin doesn't work, as it's
trying to talk to services which wouldn't be started yet. Is there any
reason why this code can't poke /etc/machine-info directly?
Cheers
On Mon, 2016-12-05 at 13:38 +0100, François Beaufort wrote:
> That's weird ;( It should be have been Google Chrome 51 according to
> https://chromium.googlesource.com/chromium/src/+/c8901b4dbb6518940e94
> /chrome/VERSION
The name got saved in the adapter's settings. I edited the "settings"
file for my adapter and it works as expected now.
Thanks
That's weird ;( It should be have been Google Chrome 51 according to
https://chromium.googlesource.com/chromium/src/+/c8901b4dbb6518940e94/chrom=
e/VERSION
On Mon, Dec 5, 2016 at 1:35 PM, Bastien Nocera <[email protected]> wrote:
> On Mon, 2016-12-05 at 13:25 +0100, Fran=C3=A7ois Beaufort wrote:
>> I believe you use an "old" build of Chrome. If you update to recent
>> version, this issue won't happen.
>> As you can see at
>> https://chromium.googlesource.com/chromium/src/+/c8901b4dbb6518940e94
>> 0213c1f94774fc04d5aa,
>> I've fixed this 8 months ago.
>
> And it seems that the fix only became available a couple of days ago in
> Google Chrome 55, which reached the stable channel.
>
>> On Fri, Dec 2, 2016 at 5:23 PM, Bastien Nocera <[email protected]>
>> wrote:
>> > Hey,
>> >
>> > Using bluez 5.43 on Fedora 25, I get:
>> >
>> > $ hciconfig hci0 name | grep Name
>> > Name: 'ChromeLinux_900A'
>> >
>> > When the PrettyHostname is:
>> > $ grep PRETTY /etc/machine-info
>> > PRETTY_HOSTNAME=3Dclassic
>> >
>> > I grepped through a bunch of things, including the firmware, the
>> > kernel
>> > sources, and bluez, but couldn't find the source of this name.
>> >
>> > I'm also fairly certain that the hostname plugin doesn't work, as
>> > it's
>> > trying to talk to services which wouldn't be started yet. Is there
>> > any
>> > reason why this code can't poke /etc/machine-info directly?
>> >
>> > Cheers
>> > --
>> > To unsubscribe from this list: send the line "unsubscribe linux-
>> > bluetooth" in
>> > the body of a message to [email protected]
>> > More majordomo info at http://vger.kernel.org/majordomo-info.html
I believe you use an "old" build of Chrome. If you update to recent
version, this issue won't happen.
As you can see at
https://chromium.googlesource.com/chromium/src/+/c8901b4dbb6518940e940213c1f94774fc04d5aa,
I've fixed this 8 months ago.
On Fri, Dec 2, 2016 at 5:23 PM, Bastien Nocera <[email protected]> wrote:
> Hey,
>
> Using bluez 5.43 on Fedora 25, I get:
>
> $ hciconfig hci0 name | grep Name
> Name: 'ChromeLinux_900A'
>
> When the PrettyHostname is:
> $ grep PRETTY /etc/machine-info
> PRETTY_HOSTNAME=classic
>
> I grepped through a bunch of things, including the firmware, the kernel
> sources, and bluez, but couldn't find the source of this name.
>
> I'm also fairly certain that the hostname plugin doesn't work, as it's
> trying to talk to services which wouldn't be started yet. Is there any
> reason why this code can't poke /etc/machine-info directly?
>
> Cheers
> --
> To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in
> the body of a message to [email protected]
> More majordomo info at http://vger.kernel.org/majordomo-info.html
On Mon, 2016-12-05 at 13:25 +0100, François Beaufort wrote:
> I believe you use an "old" build of Chrome. If you update to recent
> version, this issue won't happen.
> As you can see at
> https://chromium.googlesource.com/chromium/src/+/c8901b4dbb6518940e94
> 0213c1f94774fc04d5aa,
> I've fixed this 8 months ago.
And it seems that the fix only became available a couple of days ago in
Google Chrome 55, which reached the stable channel.
> On Fri, Dec 2, 2016 at 5:23 PM, Bastien Nocera <[email protected]>
> wrote:
> > Hey,
> >
> > Using bluez 5.43 on Fedora 25, I get:
> >
> > $ hciconfig hci0 name | grep Name
> > Name: 'ChromeLinux_900A'
> >
> > When the PrettyHostname is:
> > $ grep PRETTY /etc/machine-info
> > PRETTY_HOSTNAME=classic
> >
> > I grepped through a bunch of things, including the firmware, the
> > kernel
> > sources, and bluez, but couldn't find the source of this name.
> >
> > I'm also fairly certain that the hostname plugin doesn't work, as
> > it's
> > trying to talk to services which wouldn't be started yet. Is there
> > any
> > reason why this code can't poke /etc/machine-info directly?
> >
> > Cheers
> > --
> > To unsubscribe from this list: send the line "unsubscribe linux-
> > bluetooth" in
> > the body of a message to [email protected]
> > More majordomo info at http://vger.kernel.org/majordomo-info.html