After last night’s refresh I’m now running 2024.10.4. Attempting to update Nordpool, fmi-hass-custom and pytapo fail with:
Unable to install package nordpool==0.4.2: error: failed to create file `/snap/home-assistant-snap/637/.lock` Caused by: Permission denied (os error 13)
Unable to install package fmi-weather-client==0.4.0: error: failed to create file `/snap/home-assistant-snap/637/.lock` Caused by: Permission denied (os error 13)
Unable to install package pytapo==3.3.32: error: failed to create file `/snap/home-assistant-snap/637/.lock` Caused by: Permission denied (os error 13)
It’s apparently due some changes in core, as some people running HA inside a customized Docker have also suffered this.
In the previous latest/stable, updating Nordpool and FMI weather client failed with errors about pip’s version, so I had reverted those back to their earlier versions and put off retrying the updates until now. Pytapo could be a dependency of Tapo Camera Control, which also updated recently.
Elokuussa kerrottiin VR:n suunnittelevan yhteistyössä Itä-Lapin kuntien kanssa päiväjunayhteyttä Kemijärvelle (https://yle.fi/a/74-20107386#). Eilen VR on avannut varaukset ensi kesään saakka, mutta näitä mainittuja päiväjunia sieltä ei löydy. Pyytäisinkin siksi toimitukselta seurantajuttua aiheesta: onko nuo suunnitelmat peruttu vai mitä niille kuuluu.
I’m just making this note here publicly, since I was first going to pose this as a question, but then managed to solve it by myself:
For background, I recently switched my Mattermost from a tar archive installation to installing it from the package repository, and simultaneously switched it from using a MySQL database to using PostgreSQL, all in one fell swoop by exporting the old content, doing a fresh install, and then importing. This appears to have mostly worked, with just user profile images having been lost, and passwords requiring a reset, both of which (I’ve gleaned from various places) were to be expected.
However, all bot accounts also seem to have been converted into normal user accounts somewhere during this process. So far the only issue I’ve discovered resulting from this is this entry getting logged repeatedly:
Failed to get system bot caller="app/post.go:2205" component=post_reminders error="SqlBotStore.Get: Bot does not exist., resource "Bot" not found, id: <my system bot's id>"
I solved this by running
sudo -u mattermost mmctl user convert --bot "<bot id>" # replace <bot id> with your real system bot account id
Since that seems to have gone well (the error messages stopped), I went ahead and converted the rest of the bot accounts back to true bots likewise.
Paljon onnea parikymppiselle! Kohti seuraavia kymmenlukuja!
Luulin vielä lopussakin, että tämä oli Pieniä ihmeitä, mutta tämähän olikin näitä Silmiksen pieniä ihmeitä.
”Istahdin kävelykadun penkille, silmäilin vaivihkaa, oliko kukaan kiinnittänyt huomiota ähräämiseeni. Ei. Tässä iässä on se hyvä puoli, että on näkymätön.”
Tai sitten olivat niin kuin minä, joka ajattelen, että avun tarjoamista tärkeämpää on antaa avuntarvitsijan pitää kiinni näkymättömyydentunteestaan, koska niin itse pulassa ollessani haluaisin, vaikka ongelma olisi miten ylitsepääsemätön yksin ratkaista. Eli klassinen suomalainen ”oho, liukastuin ja pää halkesi, mutta onneksi sentään kukaan ei huomannut”.
I assume you’ve tried basic elimination, by testing with different parts & peripherals removed?
It’s a hassle of course, especially after you’ve already settled in to using the system, not to mention how tedious it is to run memtest for days on end just to achieve sufficient confidence that you’ve proved a negative.
I’m not as hardcore about this as Jeff Atwood, but I’ve learned not to discount anything as potentially being the cause or at least a trigger for all kinds of issues. Besides obvious things like RAM modules, OTOH I’ve had at least one internal memory card reader, one USB bluetooth dongle and one (SATA) SSD turn out to be the troublemaker; usually something much easier to replace than motherboard+almost everything. (And unfortunately it’s usually been easier to just replace or just get rid of the triggering component rather than hope for a software fix, even if the issue ultimately was with software.)
The cold lockups or the case being touch-sensitive don’t sound like one of those easily solvable ones, but since there’s a plethora of symptoms, perhaps some still might be, and are just hard to see from the mix.
Hep, minä seuraan, koska tykkään juuri tällaisesta klassisesta päiväkirjatyyppisestä blogista (jollaiset ovat nykyisin harmillisen harvinaisia). Eli juurikin tuo rosoinen, tavallinen elämä kiinnostaa. :)