# Bizarre behaviour 18.10 - nm-applet and bluetooth etc

**URL:** <https://discourse.ubuntubudgie.org/t/bizarre-behaviour-18-10-nm-applet-and-bluetooth-etc/1770>\
**Category:** Budgie Applets\
**Created:** [April 16, 2019, 3:47pm UTC](https://discourse.ubuntubudgie.org/t/bizarre-behaviour-18-10-nm-applet-and-bluetooth-etc/1770 "2019-04-16T15:47:06Z")\
**Posts on this page:** 16\
**Page:** 1

<div class="post-metadata">

**Author:** ![macmeister1967](https://yyz1.discourse-cdn.com/flex035/user_avatar/discourse.ubuntubudgie.org/macmeister1967/32/1178_2.png) [@macmeister1967](https://discourse.ubuntubudgie.org/u/macmeister1967)\
**Post date:** [April 16, 2019, 3:47pm UTC](https://discourse.ubuntubudgie.org/t/bizarre-behaviour-18-10-nm-applet-and-bluetooth-etc/1770/1 "2019-04-16T15:47:07Z")

</div>

I am currently testing 18.10 of Budgie, and weird stuff is happening… Wifi is actually DISABLING itself (and Bluetooth as well)… of course nm-applet completely disappears, so it may be linked to networking daemon/service???

Also, my Notifications icon is turning blue for no reason… it resets to white after clicking on it twice (usually) :-/

Anyone else see this kind of behaviour? ps. I am using Gigabyte H370 HD3 + i7-8700 + RX 580 + 16GB DDR4 2666 RAM + nvme SSDs + Samsung 850 Evo (Budgie) + 2 x 4TB storage HDD.

---

<div class="post-metadata">

**Author:** ![fossfreedom](https://yyz1.discourse-cdn.com/flex035/user_avatar/discourse.ubuntubudgie.org/fossfreedom/32/1405_2.png) [@fossfreedom](https://discourse.ubuntubudgie.org/u/fossfreedom)\
**Post date:** [April 16, 2019, 3:53pm UTC](https://discourse.ubuntubudgie.org/t/bizarre-behaviour-18-10-nm-applet-and-bluetooth-etc/1770/2 "2019-04-16T15:53:08Z")

</div>

Hi and welcome,

sounds like the 4.18 kernel isn’t playing nice with your setup.

Since you are in testing mode, it is worth testing 19.04 which is due in a couple of days time - it comes with kernel v5.

Notifications turning blue is normal when there is a notification - click on the icon and raven (the side bar) will open to list the notifications.

---

<div class="post-metadata">

**Author:** ![macmeister1967](https://yyz1.discourse-cdn.com/flex035/user_avatar/discourse.ubuntubudgie.org/macmeister1967/32/1178_2.png) [@macmeister1967](https://discourse.ubuntubudgie.org/u/macmeister1967)\
**Post date:** [April 16, 2019, 3:53pm UTC](https://discourse.ubuntubudgie.org/t/bizarre-behaviour-18-10-nm-applet-and-bluetooth-etc/1770/3 "2019-04-16T15:53:58Z")

</div>

Except there are never any notifications ☹

Can I do a dist-upgrade to 19.04?

---

<div class="post-metadata">

**Author:** ![macmeister1967](https://yyz1.discourse-cdn.com/flex035/user_avatar/discourse.ubuntubudgie.org/macmeister1967/32/1178_2.png) [@macmeister1967](https://discourse.ubuntubudgie.org/u/macmeister1967)\
**Post date:** [April 16, 2019, 3:55pm UTC](https://discourse.ubuntubudgie.org/t/bizarre-behaviour-18-10-nm-applet-and-bluetooth-etc/1770/4 "2019-04-16T15:55:09Z")

</div>

I would be interested to know HOW the OS manages to disable the hardware for WiFI and Bluetooth simultaneously?

---

<div class="post-metadata">

**Author:** ![fossfreedom](https://yyz1.discourse-cdn.com/flex035/user_avatar/discourse.ubuntubudgie.org/fossfreedom/32/1405_2.png) [@fossfreedom](https://discourse.ubuntubudgie.org/u/fossfreedom)\
**Post date:** [April 16, 2019, 3:58pm UTC](https://discourse.ubuntubudgie.org/t/bizarre-behaviour-18-10-nm-applet-and-bluetooth-etc/1770/5 "2019-04-16T15:58:01Z")

</div>

That’s the kernel itself I’m guessing.

running

```
journalctl -ae --full

```

and scrolling back should give you an idea of what is happening

---

<div class="post-metadata">

**Author:** ![macmeister1967](https://yyz1.discourse-cdn.com/flex035/user_avatar/discourse.ubuntubudgie.org/macmeister1967/32/1178_2.png) [@macmeister1967](https://discourse.ubuntubudgie.org/u/macmeister1967)\
**Post date:** [April 16, 2019, 4:07pm UTC](https://discourse.ubuntubudgie.org/t/bizarre-behaviour-18-10-nm-applet-and-bluetooth-etc/1770/6 "2019-04-16T16:07:19Z")

</div>

hmmm…

nm-applet[2165]: Can’t set a parent on widget which has a parent

and

kernel: Bluetooth: hci0: last event is not cmd complete (0x0f)

there are LOTS of the Bluetooth errors, only a few of the nm-applet errors…

---

<div class="post-metadata">

**Author:** ![macmeister1967](https://yyz1.discourse-cdn.com/flex035/user_avatar/discourse.ubuntubudgie.org/macmeister1967/32/1178_2.png) [@macmeister1967](https://discourse.ubuntubudgie.org/u/macmeister1967)\
**Post date:** [April 16, 2019, 4:10pm UTC](https://discourse.ubuntubudgie.org/t/bizarre-behaviour-18-10-nm-applet-and-bluetooth-etc/1770/7 "2019-04-16T16:10:18Z")

</div>

hmmmm, and…

bluetoothd[1130]: Failed to set mode: Blocked through rfkill (0x12)  
budgie-panel[2072]: Error setting property ‘Powered’ on interface org.bluez.Adapter1: GDBus.Error:org.bluez.Error.Blocked: Blocked through rfkill (g-io-error-quark, 36)

---

<div class="post-metadata">

**Author:** ![macmeister1967](https://yyz1.discourse-cdn.com/flex035/user_avatar/discourse.ubuntubudgie.org/macmeister1967/32/1178_2.png) [@macmeister1967](https://discourse.ubuntubudgie.org/u/macmeister1967)\
**Post date:** [April 16, 2019, 4:12pm UTC](https://discourse.ubuntubudgie.org/t/bizarre-behaviour-18-10-nm-applet-and-bluetooth-etc/1770/8 "2019-04-16T16:12:42Z")

</div>

It seems to be going OK this sessions, I disabled the two power options which allow devices to be switched off to save power (under Power settings) !!!

Save power on a desktop system?

---

<div class="post-metadata">

**Author:** ![macmeister1967](https://yyz1.discourse-cdn.com/flex035/user_avatar/discourse.ubuntubudgie.org/macmeister1967/32/1178_2.png) [@macmeister1967](https://discourse.ubuntubudgie.org/u/macmeister1967)\
**Post date:** [April 16, 2019, 4:24pm UTC](https://discourse.ubuntubudgie.org/t/bizarre-behaviour-18-10-nm-applet-and-bluetooth-etc/1770/9 "2019-04-16T16:24:04Z")

</div>

Think I found the issue… setting the two power saving options ACTUALLY DISABLES both devices 😑

[![Imgur](https://canada1.discourse-cdn.com/flex035/uploads/ubuntubudgie/original/2X/b/b49c9ea19bb295fbddad5955d1f5ec67e06fdde3.jpeg "Imgur") ](https://imgur.com/Ea2fxJd)

Also the other options change from Never to 0 seconds… which is OK if it actually works.

Thanks for your help… I’ll see how long this works

---

<div class="post-metadata">

**Author:** ![fossfreedom](https://yyz1.discourse-cdn.com/flex035/user_avatar/discourse.ubuntubudgie.org/fossfreedom/32/1405_2.png) [@fossfreedom](https://discourse.ubuntubudgie.org/u/fossfreedom)\
**Post date:** [April 16, 2019, 5:01pm UTC](https://discourse.ubuntubudgie.org/t/bizarre-behaviour-18-10-nm-applet-and-bluetooth-etc/1770/10 "2019-04-16T17:01:49Z")

</div>

Well found!

Dont know why though that those two options are enabled though … did you accidentally set then as enabled?

---

<div class="post-metadata">

**Author:** ![macmeister1967](https://yyz1.discourse-cdn.com/flex035/user_avatar/discourse.ubuntubudgie.org/macmeister1967/32/1178_2.png) [@macmeister1967](https://discourse.ubuntubudgie.org/u/macmeister1967)\
**Post date:** [April 16, 2019, 5:58pm UTC](https://discourse.ubuntubudgie.org/t/bizarre-behaviour-18-10-nm-applet-and-bluetooth-etc/1770/11 "2019-04-16T17:58:55Z")

</div>

They were showing as ENABLED, I tried to DISABLE the setting, but it disabled the HARDWARE ☹

---

<div class="post-metadata">

**Author:** ![macmeister1967](https://yyz1.discourse-cdn.com/flex035/user_avatar/discourse.ubuntubudgie.org/macmeister1967/32/1178_2.png) [@macmeister1967](https://discourse.ubuntubudgie.org/u/macmeister1967)\
**Post date:** [April 16, 2019, 6:00pm UTC](https://discourse.ubuntubudgie.org/t/bizarre-behaviour-18-10-nm-applet-and-bluetooth-etc/1770/12 "2019-04-16T18:00:01Z")

</div>

It simultaneously kills the hardware and nm-applet 👎

---

<div class="post-metadata">

**Author:** ![macmeister1967](https://yyz1.discourse-cdn.com/flex035/user_avatar/discourse.ubuntubudgie.org/macmeister1967/32/1178_2.png) [@macmeister1967](https://discourse.ubuntubudgie.org/u/macmeister1967)\
**Post date:** [April 16, 2019, 6:01pm UTC](https://discourse.ubuntubudgie.org/t/bizarre-behaviour-18-10-nm-applet-and-bluetooth-etc/1770/13 "2019-04-16T18:01:18Z")

</div>

This is the longest session I have had without the nm-applet dying, I may have solved it accidentally 😊

---

<div class="post-metadata">

**Author:** ![macmeister1967](https://yyz1.discourse-cdn.com/flex035/user_avatar/discourse.ubuntubudgie.org/macmeister1967/32/1178_2.png) [@macmeister1967](https://discourse.ubuntubudgie.org/u/macmeister1967)\
**Post date:** [April 21, 2019, 10:56am UTC](https://discourse.ubuntubudgie.org/t/bizarre-behaviour-18-10-nm-applet-and-bluetooth-etc/1770/14 "2019-04-21T10:56:25Z")

</div>

I’m going to use Budgie for one more session… and if it doesn’t happen again, I’ll mark this thread as SOLVED. Cheers.

---

<div class="post-metadata">

**Author:** ![macmeister1967](https://yyz1.discourse-cdn.com/flex035/user_avatar/discourse.ubuntubudgie.org/macmeister1967/32/1178_2.png) [@macmeister1967](https://discourse.ubuntubudgie.org/u/macmeister1967)\
**Post date:** [April 21, 2019, 6:25pm UTC](https://discourse.ubuntubudgie.org/t/bizarre-behaviour-18-10-nm-applet-and-bluetooth-etc/1770/15 "2019-04-21T18:25:41Z")

</div>

NO, it happened yet again… and again… so I am deleting Budgie and never trying it again… it’s bad enough having all my controls on my 4K monitor the size of a grain of rice… but WiFi (BCM94360CS) was nigh on unusable, and prone to spontaneous disconnection. I might try Linux (an older version not using Wayland) on some older hardware… but not like this.

---

<div class="post-metadata">

**Author:** ![fossfreedom](https://yyz1.discourse-cdn.com/flex035/user_avatar/discourse.ubuntubudgie.org/fossfreedom/32/1405_2.png) [@fossfreedom](https://discourse.ubuntubudgie.org/u/fossfreedom)\
**Post date:** [April 21, 2019, 6:28pm UTC](https://discourse.ubuntubudgie.org/t/bizarre-behaviour-18-10-nm-applet-and-bluetooth-etc/1770/16 "2019-04-21T18:28:41Z")

</div>

As I mentioned previously 19.04 has the latest kernel. It also has experimental fractional scaling support.

Anyway. Best wishes