After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 755967 - Comment for translator instead of translated label
Comment for translator instead of translated label
Status: RESOLVED FIXED
Product: gnome-bluetooth
Classification: Core
Component: properties
3.18.x
Other Linux
: Normal normal
: ---
Assigned To: gnome-bluetooth-general-maint@gnome.bugs
gnome-bluetooth-general-maint@gnome.bugs
: 756583 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2015-10-02 07:11 UTC by Dušan
Modified: 2018-01-29 08:48 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Screenshot (24.18 KB, image/jpeg)
2015-10-02 07:11 UTC, Dušan
Details

Description Dušan 2015-10-02 07:11:08 UTC
Created attachment 312542 [details]
Screenshot

For this string is displayed comment about bastien noceras computer in gnome bluetooth settings, instead of translated text.
Language: Slovak




#. translators: first %s is the name of the computer, for example:
#. * Visible as “Bastien Nocera's Computer” followed by the
#. * location of the Downloads folder.
#: ../lib/bluetooth-settings-widget.c:1222
#, c-format
msgid ""
"Visible as “%s” and available for Bluetooth file transfers. Transferred "
"files are placed in the <a href=\"%s\">Downloads</a> folder."
msgstr ""
"Zariadenie je viditeľné pod názvom „%s“ a dostupné pre prenos súborov cez "
"bluetooth. Prenesené súbory sú umiestnené v priečinku <a href=\"%s"
"\"Stiahnuté</a>."
Comment 1 Bastien Nocera 2015-10-02 11:06:37 UTC
This means your system is broken, slightly.

What's the output of:
rfkill list
hciconfig
Comment 2 Dušan 2015-10-02 12:20:07 UTC
rfkill list output:

0: hci0: Bluetooth
	Soft blocked: yes
	Hard blocked: no
1: phy0: Wireless LAN
	Soft blocked: no
	Hard blocked: no



hciconfig output:

hci0:	Type: BR/EDR  Bus: USB
	BD Address: 00:1A:7D:DA:71:13  ACL MTU: 310:10  SCO MTU: 64:8
	DOWN 
	RX bytes:574 acl:0 sco:0 events:30 errors:0
	TX bytes:368 acl:0 sco:0 commands:30 errors:0
Comment 3 Bastien Nocera 2015-10-02 12:46:01 UTC
What's the output of:
gdbus introspect --session --dest org.gnome.SettingsDaemon.Rfkill --object-path /org/gnome/SettingsDaemon/Rfkill
when the problem happens?

What happens if you plug the Bluetooth dongle in when logged out of the session?
Comment 4 Dušan 2015-10-02 12:55:58 UTC
output:

node /org/gnome/SettingsDaemon/Rfkill {
  interface org.freedesktop.DBus.Properties {
    methods:
      Get(in  s interface_name,
          in  s property_name,
          out v value);
      GetAll(in  s interface_name,
             out a{sv} properties);
      Set(in  s interface_name,
          in  s property_name,
          in  v value);
    signals:
      PropertiesChanged(s interface_name,
                        a{sv} changed_properties,
                        as invalidated_properties);
    properties:
  };
  interface org.freedesktop.DBus.Introspectable {
    methods:
      Introspect(out s xml_data);
    signals:
    properties:
  };
  interface org.freedesktop.DBus.Peer {
    methods:
      Ping();
      GetMachineId(out s machine_uuid);
    signals:
    properties:
  };
  @org.freedesktop.DBus.GLib.CSymbol("gsd_rfkill_manager")
  interface org.gnome.SettingsDaemon.Rfkill {
    methods:
    signals:
    properties:
      readwrite b AirplaneMode = false;
      readonly b HardwareAirplaneMode = false;
      readonly b HasAirplaneMode = true;
      readonly b ShouldShowAirplaneMode = false;
      readwrite b BluetoothAirplaneMode = false;
      readonly b BluetoothHardwareAirplaneMode = false;
      readonly b BluetoothHasAirplaneMode = true;
  };
};


tried logging out/pluggin in/out dongle, still is there label with your name and in english
Comment 5 Bastien Nocera 2015-10-02 13:26:21 UTC
Not sure why, but:
      readwrite b AirplaneMode = false;
      readonly b HasAirplaneMode = true;

Should be AirplaneMode = true, as hci0 is soft-blocked. Not sure why that would be the case... Anyway, I've hit this bug often enough that I'll need to make some UI changes for it.
Comment 6 Bastien Nocera 2015-10-14 18:21:23 UTC
*** Bug 756583 has been marked as a duplicate of this bug. ***
Comment 7 Michael Biebl 2015-10-14 19:30:04 UTC
Bastien's hint to check rfkill, revealed:

$ rfkill list
0: tpacpi_bluetooth_sw: Bluetooth
	Soft blocked: no
	Hard blocked: no
1: tpacpi_wwan_sw: Wireless WAN
	Soft blocked: no
	Hard blocked: no
3: phy0: Wireless LAN
	Soft blocked: no
	Hard blocked: no
6: hci0: Bluetooth
	Soft blocked: yes
	Hard blocked: no


unblocking 6 (rfkill unblock 6), did make my computer name show up in the sharing panel.



Disabling bluetooth via gnome-control-center results in

$rfkill list
0: tpacpi_bluetooth_sw: Bluetooth
	Soft blocked: yes
	Hard blocked: no
1: tpacpi_wwan_sw: Wireless WAN
	Soft blocked: no
	Hard blocked: no
3: phy0: Wireless LAN
	Soft blocked: no
	Hard blocked: no

And re-enabling bluetooth (via gnome-control-center) results in
$ rfkill list
0: tpacpi_bluetooth_sw: Bluetooth
	Soft blocked: no
	Hard blocked: no
1: tpacpi_wwan_sw: Wireless WAN
	Soft blocked: no
	Hard blocked: no
3: phy0: Wireless LAN
	Soft blocked: no
	Hard blocked: no
6: hci0: Bluetooth
	Soft blocked: yes
	Hard blocked: no

and I'm back at step one (i.e. hci0 is again block for some reason)
Comment 8 Bastien Nocera 2015-10-14 20:02:26 UTC
I think that it's a race, basically. When we unblock tpacpi_bluetooth_sw, hci0 takes some time to reappear, and doesn't get unblocked. What should be happening, is that hci0 comes back up unblocked.

Which version of systemd are you using? Is it systemd 227?

If so, this change is to blame: 

        * systemd-rfkill has been reworked to become a singleton
          service that is activated through /dev/rfkill on each rfkill
          state change and saves the settings to disk. This way,
          systemd-rfkill is now compatible with devices that exist
          only intermittendly, and even restores state if the previous
          system shutdown was abrupt rather than clean.
Comment 9 Michael Biebl 2015-10-14 20:11:26 UTC
I do indeed run systemd 227
Comment 10 Dušan 2015-10-14 20:13:13 UTC
I am running systemd 226
Comment 11 Bastien Nocera 2015-10-15 12:22:19 UTC
Might not be systemd then. Which versions of bluez are you using?
Comment 12 Dušan 2015-10-15 19:53:26 UTC
bluez is v5.35
Comment 13 piotr.pejas 2015-11-01 23:49:19 UTC
It looks to be related to status of bluetooth.service
When it's turned off:
# systemctl stop bluetooth
Visible as “Bastien's computer” and available for Bluetooth file transfers. Transferred files are placed in the Downloads folder.

Downloads -> Copy Link Address = http://www.gnome.org

and on
# systemctl start bluetooth
Visible as “plpp” and available for Bluetooth file transfers. Transferred files are placed in the Downloads folder.

Downloads -> Copy Link Address = file:///home/xxx/Pobrane

plpp is my computer hostname
file:///home/xxx/Pobrane is my Downloads dir

I've run bluetooth applet from command line:
LANG=C gnome-control-center

When LANG=pl_PL.utf8 and bluetooth service is on I am getting "right" message in polish, when off same as with LANG=C.

Arch linux
gnome-bluetooth 3.18.0-1 
bluez 5.35-1
systemd 227-1
Comment 14 Dušan 2015-11-25 09:36:30 UTC
I have now correct label in bluetooth settings (reason why i have created this issue). using gnome-bluetooth 3.18.1
Comment 15 Bastien Nocera 2016-01-04 13:51:08 UTC
The later problems are due to changes in newer versions of bluez and the kernel, which instead of unblocking the rfkill when SetPowered is called will fail saying that the rfkill was on, so won't turn the device on.

We'll be tracking this problem in bug 741675.
Comment 16 Paul Wise 2016-04-27 09:04:43 UTC
Looks another string saying “Bastien's computer” and having the wrong Downloads link was missed:

https://git.gnome.org/browse/gnome-bluetooth/tree/lib/settings.ui#n387
https://codesearch.debian.net/search?q=package%3Agnome-bluetooth+Bast.*omputer
Comment 17 Bastien Nocera 2016-04-27 09:09:23 UTC
(In reply to Paul Wise from comment #16)
> Looks another string saying “Bastien's computer” and having the wrong
> Downloads link was missed:
> 
> https://git.gnome.org/browse/gnome-bluetooth/tree/lib/settings.ui#n387
> https://codesearch.debian.net/search?q=package%3Agnome-bluetooth+Bast.
> *omputer

So what? You saw it in the UI? You're just slinging mud, and wasting my time (on multiple bugs at that). And if you saw it, file a new bug.
Comment 18 piotr.pejas 2016-04-27 13:58:51 UTC
Please read and follow "GNOME Code Of Conduct"

https://wiki.gnome.org/action/show/Foundation/CodeOfConduct?action=show&redirect=CodeOfConduct
Comment 19 Paul Wise 2016-04-28 05:04:11 UTC
I saw it in the UI. I wouldn't have posted a message without seeing a problem, seeing it had already been reported in multiple places and fixed in both upstream and Debian and investigating why it wasn't fixed for me.

If I violated the code of conduct or did any mud slinging, it wasn't intentional and I apologise.

I don't seem to be able to reproduce the issue right now (I could, but turned bluetooth on and off a couple of times and it went away), but I'll file a new bug if I see it again.

However, the string that started this bug report is still present in the source code, so I would recommend that be fixed whether or not I file a new bug report.
Comment 20 Bastien Nocera 2016-04-28 09:12:19 UTC
(In reply to Paul Wise from comment #19)
> However, the string that started this bug report is still present in the
> source code, so I would recommend that be fixed whether or not I file a new
> bug report.

That what be fixed? Of course the string is still present, it's a placeholder!
(and the other one is in a comment...)