As per title. A post on NixOS users’ Discourse implicated XDG_TEMPLATES_DIR, although that one was about a bug in Glib newer than what’s in Ubuntu 24.04, involving trailing slashes. But I had mine pointed to $HOME/tmp, and apparently Nautilus tries to read all the garbage files I have therein, almost choking to death while doing so.
I made a separate, new (empty) directory, pointed XDG_TEMPLATES_DIR to it, killed all existing Nautilus processes and hallelujah! It’s no longer slow.
(This post is just a bit of good old-fashioned search engine fodder. Systemd terminology is frustratingly generic, making it hard to find solutions to specific problems related to it.)
I’m trying out per-user units for the first time, and immediately wanted to also use top-level drop-ins. I couldn’t find solid documentation for it, but logically, I assumed they would go under ~/.config/systemd/user/service.d/.
This didn’t seem to work though: systemctl --user cat $unitname still only listed the contents of $unitname.service without what I had in ~/.config/systemd/user/service.d/override.conf.
After flailing around for a while, I realized I just had to do a systemctl daemon-reload --user to make it work.
(I don’t know if the support for top-level drop-ins in per-user units was already there when user units themselves arrived, but at least it’s working for me in Ubuntu 24.04 with systemd version 255.)
I recently set up my local mail to go into ~/Maildir. But when logging in on a console, the mail notification under motd still seemed to assume my mail being somewhere else (under /var/mail maybe), as it only ever said
You do not have any new mail.I figured out that this message is generated by pam_mail, and it’s possible to configure it to use ~/Maildir with the dir= parameter. There’s separate configuration for each of (local) login, ssh and su in /etc/pam.d/login, /etc/pam.d/sshd and /etc/pam.d/su respectively. For instance, /etc/pam.d/login has this line:
session optional pam_mail.so standardwhich I changed to
session optional pam_mail.so dir=~/Maildir standardand now the note under motd reflects what’s in my ~/Maildir.
Mutt settings are mostly inscrutable to me, so I’ll just dump the ones I found (through trial and error) that do what I want below. Besides having these:
set sort=threads
set sort_browser=reverse-date
set sort_aux=reverse-last-date-receivedI needed to add these:
set sort_re=no
unset strict_threadsFor convenience, I also added these:
# Collapse threads at startup
exec collapse-all
# Set the keys for un-/collapsing all threads/one thread
bind index _ collapse-all
bind index - collapse-thread(I’m using Mutt version 2.2.12 in Ubuntu 24.04.)
After upgrading all Ubuntu 18.04 packages to their latest releases, I adapted eudoxos‘ recipe:
debian-keyring and debian-archive-keyring .debs and installed them with dpkg -i debian*.deb/etc/apt/preferences.d/10-no-ubuntu to pin down Ubuntu packages:
Package: *
Pin: release o=Ubuntu
Pin-Priority: -1000/etc/apt/sources.list:
deb http://deb.debian.org/debian buster main contrib non-free
deb http://deb.debian.org/debian-security/ buster/updates main contrib non-free
deb http://deb.debian.org/debian buster-updates main contrib non-freeapt update && apt-get dist-upgradesystemctl disable apparmor.service) and rebooted./etc/apt/preferences.d/10-no-ubuntudpkg -l | grep ubuntuand
aptitude search '?narrow(?installed, ?not(?origin(Debian)))'Many of the matching packages can be removed/downgraded to their Debian versions without issue, but a bunch of gcc and python packages turned out to be tricky, and had to be downgraded all together. I did make notes, but following them blindly would most likely just do more harm than good, so I won’t post them here; you’ll need to hack’n’slash your own way anyway.
XDA-foorumin anandmoren ohjeen mukaisesti:
Just a note for myself about this: Bug 1863246: Copy and Paste context menu entries are sometimes disabled when they should not be
And a workaround lower down, from lexlexlex:
“I noticed that an easy workaround when this happens is to click the address bar to change selection focus, then interact with the page again. After that, the “Copy” entry in the context menu works again without reopening the tab.”
One thing that was confusing to me from the start was the seemingly overlapping functionality in __init__.py and config_flow.py, but I think I figured it out: async_step_*() in config_flow.py is for when a component is first set up, whereas async_setup_entry() in __init__.py is for when a config entry for the component has already previously been set up, and so an object can be instantiated for that entry.
As for “my API”, my impression (from both core and non-core integrations) is that if I had a published Python package for the device, I’d just import it (like, for instance, RuuviTag integration imports ruuvitag-ble), but if/as I don’t, I should create the API in a subdirectory of my integration and import it using dot notation.
Hence, naming the files inside the API directory is more a question of general Python convention, rather than something HA has opinions about.
Anyway, while I understand all the complications I keep stumbling over make HA component development scalable, it also makes my tiny button project way more complicated than it should be. There appears to be no way to build a minuscule MVP with just a few lines of code, to be then extended with all the bells and whistles that would make it look and play nice.
Instead it seems easier to just hack some existing code to work with my device (which I’ve already done, semi-successfully). But that means then having to clean up tons of someone else’s code, or, what’s more likely, just leave it all as an ugly hack, never to be published anywhere.
systemctl edit getty@tty1.service[Service]
ExecStart=
ExecStart=-/bin/journalctl -b -ef
StandardInput=tty
StandardOutput=ttysystemctl daemon-reload followed by systemctl restart getty@tty1.service/etc/default/grub, add consoleblank=0 to GRUB_CMDLINE_LINUX_DEFAULT, save and exit. Then run update-grub and reboot.(I adapted the service override from Remy’s old post.)
The documentation keeps referring to “my API”, but leaves everything about it up to imagination. How should I name the file? What code should I put there, and what should I not?
The MyEvent example, which I adapted for my event.py, keeps failing to load, because it “has no attribute ‘async_setup_entry’”. I get it to shut up by adding a dummy by that name as a function — not as a method.
I grab some logging code from someone else’s Bluetooth integration and adapt it to my _async_has_devices(), to see if I need to do any actual filtering. But none of it ever gets run, despite HA announcing a device being detected by my integration.
In the end I decide it’s not going to be as easy as I’d hoped with the config_flow_discovery scaffolding. I’m going to have to invoke Bleak to be able to subscribe to BLE notifications, which are what my button uses to communicate press events, and which, apparently, are not part of HA core for now. So I revert the config_flow.py changes and go back to the longer version.
The first TODO there is for user data schema. I won’t have users input any configuration, so out it goes, as does all of validate_input(), and async_step_user() in ConfigFlow. Likewise for PlaceholderHub (“Remove this placeholder class and replace with things from your PyPI package”).
According to “Discovery steps“,
“When an integration is discovered, their respective discovery step is invoked (ie async_step_dhcp or async_step_zeroconf) with the discovery information.”
This means it should be async_step_bluetooth() for mine. I wish it was listed, along with all other variants, instead of just the two examples, to help googling. An accompanying example would be even better.
The last item on the list of things the discovery step should do is:
“Invoking a discovery step should never result in a finished flow and a config entry. Always confirm with the user.”
Again, not even a hint about this in the documentation, but most core integrations appear to implement a async_step_bluetooth_confirm(), and call it at the end of async_step_bluetooth(). There’s also _set_confirm_only(), which seems like what I need, but again, no documentation anywhere.