Skip to content

Microsoft Sticky Notes Alternative Windows 10

After upgrading many clients to Windows 10, we ran into multiple issues with Microsofts Sticky Notes. Notes are "lost", Sticky Notes stopped working or has been removed by the system or what ever.

Simply Sticky Notes is our decided alternative.

Benefits are:

  • multiple language support
  • lightweight
  • contains backup mechanism
  • notes are stored in a sqlite database
  • you can move the storage path wherever you want
    Translate to de es fr it pt ja

Nextcloud Client 3.0.1 on Linx >> there are unresolved conflicts<<

As written in the official issue ticket, following the way how to solve your conflict locally.

A quick update to figure out the conflicted files. cd into your nextcloud synchronized path

#list conflicted files 
find . -iname *conflic* -type f

You can than decide which file is the one you want to keep foo.bar or foo (conflicted copy 2020-09-09 083407).bar.

See also here and here.

Translate to de es fr it pt ja

Check which version and fix pack of your HCL Notes / IBM Notes is installed

Today I needed to create a skript that automatically installes a Notes FP (Fix-Pack) to all our clients.

The windows registry, as example, does not tell which of if there is a FP installed. After a while, my current solution is to check which value the variable FaultRecovery_Build inside the notes.ini is containing.

#pseudo code
$fp5IsInstalled = (cat notes.ini | grep -q "Release 10.0.1FP5")
If ($fp5IsInstalled) {
    //... do something or nothing
}

Hope this helps.

Translate to de es fr it pt ja

`error: archzfs: signature from "ArchZFS Bot <buildbot@archzfs.com>" is unknown trust` and how to solve it

I ran into this error error: archzfs: signature from "ArchZFS Bot <buildbot@archzfs.com>" is unknown trust on multiple machines over the last days.

Since one machine was working which is also running one of my dns servers, I was searching into this direction. After a while, I switched all my machines using this one dns server without fixing the real issue. Furthermore, by just trying to refresh keys with sudo pacman-key --refresh-keys, I ran into another error: gpg: WARNING: Tor is not running.

I could solve this with a one liner:

echo "no-use-tor" >> ~/.gnupg/dirmngr.conf

Next step was finally to delete the broken key and re-import ist again.

sudo pacman-key -d DDF7DB817396A49B2A2723F7403BD972F75D9D76
sudo pacman-key -r DDF7DB817396A49B2A2723F7403BD972F75D9D76
sudo pacman-key --lsign-key DDF7DB817396A49B2A2723F7403BD972F75D9D76

After running through all this steps, I was able to run a system update again with pacman.

Thanks to this issue report on github, this entry on redit and this entry on gnupg.org.

Translate to de es fr it pt ja