[Bug 1797322] Re: gsd-rfkill-manager fails to receive rfkill event

[Brian Murray]

Hello ethan.hsieh, or anyone else affected,

Accepted gnome-settings-daemon into bionic-proposed. The package will
build now and be available at https://launchpad.net/ubuntu/+source
/gnome-settings-daemon/3.28.1-0ubuntu1.1 in a few hours, and then in the
-proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-bionic to verification-done-bionic. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-bionic. In either case, without details of
your testing we will not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: gnome-settings-daemon (Ubuntu Bionic)
       Status: New => Fix Committed

** Tags added: verification-needed verification-needed-bionic

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1797322

Title:
  gsd-rfkill-manager fails to receive rfkill event

Status in OEM Priority Project:
  Confirmed
Status in gnome-settings-daemon package in Ubuntu:
  Fix Released
Status in gnome-settings-daemon source package in Bionic:
  Fix Committed

Bug description:
  [Impact]

  The default encoding for GIOChannel is UTF-8, but rfkill event is
  binary data. gsd-rfkill-manager will fail to receive rfkill event if
  rfkill-idx is larger than 127.

  Settings will always shows Bluetooth is off after resume.

  The solution is to set the encoding of GIOChannel as NULL (binary
  data).

  [Test Case]

  1) Enable the -proposed repository, and install new "gnome-settings-
  daemon-schemas" and "gnome-settings-daemon"

  2) Reboot system

  3) Run suspend/resume test more than 127 times and then check if BT
  settings still works well.

  [Regression Potential]

  Low. The default encoding for GIOChannel is wrong. Just set correct
  encoding to receive rfkill event.

  ---

  The default encoding for GIOChannel is UTF-8, but rfkill event is
  binary data. If the value is invalid UTF-8, gsd-rfkill-manager will
  fail to receive rfkill event.

  Steps: Run suspend/resume Test (> 127 times)
  Failure Rate: 100%

  In some platforms, bt will be re-probed after s3. If bt is re-probed,
  rfkill-idx will increase. And, 128 is the first invalid UTF-8

  $ rfkill list
  ID TYPE DEVICE SOFT HARD
  1 wlan phy0 unblocked unblocked
  128 bluetooth hci0 unblocked unblocked

  Error Message:
  gnome-settings-daemon/plugins/rfkill/rfkill-glib.c
  gsd-rfkill[2062]: event_cb: 1 g_io_channel_read_chars
  gsd-rfkill[2062]: g_io_channel_fill_buffer: cur_len=0, read_size=8
  gsd-rfkill[2062]: g_io_channel_read_chars: 5 *bytes_read=8
  gsd-rfkill[2062]: event_cb: 1 read=8
  gsd-rfkill[2062]: event_cb: 1 source->read_buf->len=0
  gsd-rfkill[2062]: event_cb: 1 source->encoded_read_buf->len=0
  gsd-rfkill[2062]: RFKILL event: idx 127 type 2 (BLUETOOTH) op 1 (DEL) soft 0 hard 0
  gsd-rfkill[2062]: event_cb: 2 g_io_channel_read_chars
  gsd-rfkill[2062]: event_cb: 2 read=0
  gsd-rfkill[2062]: event_cb: 2 source->read_buf->len=8
  gsd-rfkill[2062]: event_cb: g_list_length=1
  gsd-rfkill[2062]: Removed Bluetooth rfkill with ID 127
  gsd-rfkill[2062]: event_cb: 1 g_io_channel_read_chars
  gsd-rfkill[2062]: event_cb: 1 read=0T
  gsd-rfkill[2062]: event_cb: 1 source->read_buf->len=16
  gsd-rfkill[2062]: event_cb: g_list_length=0

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1797322/+subscriptions