Hey @worldofpeace, I’m a little late to the party, but I thought I could share something.
(Context: I am coming back to Linux after 4 years on macOS and I am excited by how some things have changed over this time and at the same time a little bummed by seeing that a lot of really basic stuff still has not been sorted out yet. Like scrolling. I just can’t believe that 4 years is not enough to make scrolling work sanely. But I am willing to put effort in helping fix all this.)
So, I have NixOS 20.09 with Pantheon and it greets me with a “fail whale” on login from time to time, however it is usually resolved by logging in on the console and restarting display-manager
. I have absolutely no idea why this happens but it is just rare enough not to be annoying, so I don’t bother looking into the cause.
There also seems to be something wrong when locking the screen. When I press “lock” it changes to a black screen and there is literally nothing on the screen or in the logs for around 10 seconds. And then lightdm appears, and then a whole bunch of overall normal-looking log messages. During those 10 seconds I see some NetworkManager and systemd-related messages in dbus-monitor
, so the system is alive and I suspect some of those messages might be the key, but there are a lot of them and they are really hard to analyse.
And then there is Bluetooth… I mean, yes, Bluetooth on Linux is a running joke (and I have to say on macOS it is even worse, because not only it doesn’t work sometimes, but there is also absolutely nothing you can do to change this). But the things I am struggling with seem to be pretty high-level.
One annoying thing is that Bluetooth keeps switching off when I suspend/resume the laptop and even when I simply lock it(!). I looked at dbus-monitor
and I am pretty sure I saw someone send a message to switch it off when I am locking the screen, but dbus-monitor
does not make it easy to identify what process that was. There is some irony in that when I tried to google this problem, it looks like everyone else is struggling with their Bluetooth switching ON after every login even though they don’t want it.
While looking into this I noticed that if I switch Bluetooth ON/OFF with dbus-send
myself, after Bluez broadcasts a signal with the status update, wingpanel sends another message to it to switch ON/OFF. I don’t think this causes any issues, since it is trying to set it to the same state that I have just set myself, but that’s just a weird thing to do, and I suspect this might indicate some potential bug. I guess, I’ll just report this to the bluetooth indicator upstream.
Another issue I am experiencing just doesn’t make any sense at all. I have a bluetooth keyboard and a bluetooth trackpad. After I login and switch bluetooth on manually (since it keeps switching off all the time), I press a key on the keyboard and it reconnects; then I touch the trackpad and it tries to reconnect, but fails – I see it become green and then grey again in the drop-down list of devices. No matter how many times I try, it can’t connect. However! If I open Bluetooth Settings and touch the trackpad again, it will connect successfully. I have no explanation for this, and I have no idea where even to start looking.
Finally, sometimes Bluetooth devices get duplicated in the drop-down list. I think this has been fixed in the indicator master back in May, however they haven’t made a release yet. So, I guess, my question here is: is there a specific policy on which version of Pantheon packages we use in NixOS? Should we switch to just following their master branches or use the released version and include specific bug fixes as patches?
And in general, what would be the appropriate space to discuss and look for help with issues like this? I imagine, Elementary OS won’t be happy to receive my bug reports, and rightfully so, since it is pretty likely that some of what I am seeing is NixOS-specific.