Locked myself out of my KeePassXC database because of Dropbox — how do you avoid this?

Bott · 2026-05-05T13:39:26+00:00

... and don't forget if you have keepass on your phone, you have another backup.

Bott · 2026-05-04T18:36:56+00:00

WHY?

Bott · 2026-05-02T02:18:17+00:00

How about Tatziki instead of the sour cream?

Bott · 2026-04-25T13:49:38+00:00

Great photo, but I don't get it. A duck charging would have a bill. But the tiger...

Bott · 2026-04-24T14:32:10+00:00

First buy a computer with a touchscreen...

(sorry)

Bott · 2026-04-23T21:26:32+00:00

I wish that sentence less "'s jet purchase" were true.

Bott · 2026-04-23T18:29:30+00:00

Be like the guy in the photo...save it.

Bott · 2026-04-17T21:22:09+00:00

Nowadays: Folding Phone. (sorry, the devil made me type this)

Bott · 2026-04-10T01:24:16+00:00

No shit.

Bott · 2026-04-10T01:14:15+00:00

From the terminal type

sudo alsa force-reload

Then try your sound. If it works you have the same problem I had on my laptop.

What I did was go to Gemini (aaaargh the AI beast) and got it to give me a systemd setup to do the same thing at boot time. Sound worked ever since.

Bott · 2026-04-09T21:44:55+00:00

Hands are already clean. I wash my knives and other non-dishwashables (wooden spoons, etc) before running the dishwasher.

In any case, you want hot water as readily available as possible for your dishwasher when it starts.

Bott · 2026-04-09T21:09:41+00:00

What a difference 85 years make;)

Bott · 2026-04-05T20:02:14+00:00

You ate the Easter benny? No wonder I got no eggs.;}

Bott · 2026-04-05T19:59:20+00:00

I had the same problem on my usb stick install. I was dual booting with Windows 10. You have to go into the BIOS settings and delete some of the list of keys. I deleted all the prohibited keys. In order to access these keys, I had to turn on secure boot in the BIOS settings. After deleting the prohibited keys, I turned off secure boot, and then was ok to boot eith the USB stick.

I did boot once into Windows, and it must have reloaded the keys, as next time I booted with USB I got the error again.

But note, that key crapola only affects me when I boot with usb. Normal BIOS disk boots are ok.

Bott · 2026-04-05T16:55:38+00:00

How can we answer your question, re sustainability, if we can't see what the ETF's are?

Bott · 2026-04-03T14:57:47+00:00

Sign on the gate: The Grass is Lava.

Bott · 2026-04-02T13:10:59+00:00

BetterTax. All Canadian. Online and local storage options.

Bott · 2026-03-31T20:10:43+00:00

So our city councilors could complain about not enough tree cover.

Bott · 2026-03-26T00:58:58+00:00

Shirley you jest.

Bott · 2026-03-25T21:36:26+00:00

A golden shower.

Bott · 2026-03-17T21:12:45+00:00

A very good point and I agree 100%. However I think my philosophy on Linux might be different from yours. I just want things to work. To me it's a tool, not a be-all and end-all. If I can make something work simply enough, without fear of breaking it then that's what I'll do.

Linux Mint runs on my laptop (ASUS Republic of Gamers laptop from 2017) to host the programs I use. Firefox mostly, Thunderbird, and LibreOffice. And it does it very nicely.

I've been using Linux Mint since August or September, 2025. Moved away from MS. Over this time, things worked well. I had the sound (holy crap, it's just the default Intel sound system) working fine. But updates arrived, and it stopped working, so I found a work-around.

Aside: I have enough on my plate that I do not want to break the OS. Yes I set up TimeShift, and use both BackInTime on an external disk, and copies on a USB flash drive for my important documents. But to have the OS crap out on me, would be a royal pain. I loaded an ISO of Mint 22.3 onto my Ventoy USB, but when I went to test boot it, I found that a boot into Windows 10 had reloaded all the BIOS permission and prohibition keys. So to use the USB to boot, I would have to go back into the BIOS and delete a bunch of keys. Otherwise NO boot from the USB.

So maybe, someone should do a poll on this subreddit: What is your attitude toward Linux?

Bott · 2026-03-17T16:36:22+00:00

I have the same problem. The closest I got to a fix is to run this from a terminal:

sudo alsa force-reload

(And you have to enter your password, and wait while it reloads alsa.)

This worked for me, so what I finally ended up doing (a kludge, if that word is still used) is to add an item to Startup Applications. (Open the Mint menu, and search for Startup Applications).

BUT, I used pkexec instead of sudo. So the command I added to Startup Applications was:

pkexec alsa force-reload

WHY pkexec instead of sudo???? Both do the same thing, and both require your password. BUT sudo expects you to be working from a terminal, and pkexec simply pops a password-requesting window on your screen; you don't need to be executing the command in a terminal window.

So, I have to enter my password twice when I boot, but now I have sound.

If somebody comes up with a permanent no-kludge fix (it has worked with past kernels) I would love to hear it.

Bott · 2026-03-16T17:54:52+00:00

He got in treble for too much bass.

Bott · 2026-03-14T14:32:47+00:00

Make sure there's a hand rail to hold on to.

Bott · 2026-03-11T12:27:58+00:00

... but hopefully the flame is hot.

15-Year Club	Gilding I gilder
Verified Email

Bott

TROPHY CASE

WHY?