Danielle Foré
Danielle Foré
This is because Bluez doesn't keep a global memory of bluetooth status. The bluetooth indicator tries to keep a memory per user and the greeter is its own user
I wish I had left a little more context here. I'm guessing this was in response to something a user said somewhere?
Gonna close this since it would break convention
Yeah bluetooth indicator probably makes sense since it's bluetooth aware and exists pretty much always
I don't think the indicator can grab key events when it's not focused. We probably need to do this in Gala. Mentioning @donadigo to see if that's right
So what we need here is to create some kind of DBus API so that the notification server can find out if the notifications indicator is open. We also have...
can you clarify what you mean by "a large amount"? I can't seem to reproduce this Closing as "incomplete" until this can be reproduced You can manually clear the notification...
Okay yup, I can confirm for 2,000 notifications that we have a freeze here
For the curious a quick way to reproduce is `for n in {1..2000}; do notify-send test test; done`
Seems like https://github.com/elementary/wingpanel-indicator-notifications/pull/142 helps with this considerably