2ton_jeff

So I bought a Nokia G22 to replace my old Galaxy, and it has not gone well. I did enjoy hearing the Nokia chime for the first time in nearly 2 decades though, haha.

Deal breaker first and foremost: Nokia/HMD Global Oy has apparently decided not to license any MicroSD storage filesystem, and declares ext4 as a non-portable filesystem and rejects it too. This means that the ONLY filesystem format it will deal with on a MicroSD is FAT32. So my 256GB space shows up correctly as "250GB" but I can't for example store my Signal backup on it because it is >4GB. The device itself's camera is readily capable of storing files larger than 4GB but you can't store that on your own MicroSD either.

Second thing that nearly was a deal-breaker: For reasons unknown, Signal doesn't end up correctly whitelisted for the Android deviceidle feature regardless of all UI-based battery settings/disabling/etc. This means Signal notifications arrive every 10 minutes, and for most people I know including non-technical family, this is unacceptable. The fix requires developer tools and adb: adb shell dumpsys deviceidle disable It is interesting that "org.thoughtcrime.securesms" is indeed in the whitelist, it just doesn't work.

So since this phone was only just released here in Australia, I reached out to their AU support and asked for a refund due to the fact that their MicroSD is basically useless to me. This was their reply: Hi Jeff,

  Thank you for your email and for bringing this to our attention.

  We shall pass on your comments to our product design team.

  Unfortunately as the Nokia G22 is not faulty and works as designed we cannot issue a replacement or refund.
 
  Kind regards,

  Nokia Care Team Australia

I have used openSUSE as my daily driver for many years, and today took my Leap 15.2 to 15.3. All of that worked fine and as expected, UNTIL I LOGGED OUT.

I cried actual tears of furious rage today at whoever thought this: https://github.com/systemd/systemd/blob/main/src/shared/clean-ipc.c was a good idea.

I routinely treat /dev/shm as a "that will persist until this machine loses power or is rebooted." Apparently, on April 13th, one or more twits dealing with systemd decided that I no longer get to treat /dev/shm that way.

I am trying my best to remain calm as I write this, but the aforementioned code deleted not only my primary operating directories, but ALL Of my locally attached backups as well.

In all, 24TB of BADLY deleted "rm -rf" but without deleting the directories was done, in about 21 minutes before I realised what was happening.

I now have empty directories of all of my client working directories, all of my multimedia drives that our family uses at night, all of the original writes of the births of my children... all because someone decided that removing POSIX shared memory directories when I logout belongs to systemd and not me.

FAR OUT man.

Fortunately, I have a nightly that does backups to an external machine, but it is REMOTE, and now has to do a FULL COPY of the entire thing. I am typing this from my missus' lappy while it presumably will take many days to restore.

Case end point: I only really lost today, tomorrow and maybe the next day worth of billable productivity as a result, but ONLY because I have an external nightly backup running. Local backups (which mirror all local content) were all compromised because I mount them the same way inside /dev/shm.

openSUSE/SLES/SUSE itself is not to blame, the change is a systemd change and all of the major systemd distros will do the same thing to you.

Caveat emptor.