Looks like I’m on 1password 8 in Linux. For whatever reason, I just prefer the app instead of having the browser pop open 1password.com to edit records. I don’t know why, it just bugs me. I know part of it is that I want to use the native app to show support for it.

The plugin works fine, but it can’t call the separate program if you have that installed.

Because I wanted it to integrate with 1password full client.

Every time this is asked, I post the same comment. I used Kubuntu for years and liked it, but more recently they started doing things that annoyed me. The biggest was related to snaps and Firefox. Now, sandboxing a browser is probably a great idea, but I wanted to use the regular deb install, so I followed the directions to disable the snap install and used the deb. However, Ubuntu overrode that decision several times - I’d start browsing, then realize I was using a snap AGAIN. Happened a few times over a couple years. If it happened once, eh, maybe an error, but it happened 3 or 4 times. I came to the conclusion I wasn’t in control of my system, Ubuntu was.

I switched to Debian and am happy with my choice.

I gave up running an email server long ago - I thought it was basically impossible because too many spammers were doing it for nefarious purposes.

I came across a bowling arcade game that ran Linux. Still kind of wishing I’d bought it.

Pretty sure it’s this one.

Pretty much. Oh but the updated dependency required for your new program breaks an old program you’ve been relying on for years!

“If you want to know how Linux works, ask a Slackware user.”

I’ve mentioned this a lot lately, but I used Slackware from the late 90s (3.x days) until about 2009 on my desktop and laptop, and about 2017 on my server. I just got tired of dealing with dependencies and switched to Debian (all three run Debian now). I had the CD subscription and would automatically receive the latest version about twice a year.

Patrick Volkerding (if my memory is accurate) has my utmost respect, and I do feel a little bad about abandoning it, but I just didn’t have the time to deal with it any more.

That reminds me - for my Lenovo laptop, no issues at all with suspend and resume (just like Kubuntu). But my desktop was going to sleep when I first installed Debian, and it was NOT waking up gracefully; in fact I had to reboot it each time. Since I didn’t want it to go to sleep at all, I didn’t attempt to diagnose the issue beyond turning off the suspend mode in power management.

I just had to change a few things - KDE, dark mode, X11 when I couldn’t get screen power off to work under Wayland, and it’s basically good to go. There might be a few other things I changed, but in general out of the box was pretty close to what I wanted. It even installed the AMD driver for my graphics card.

That sounds like it’s mostly about the default install, and I don’t have a problem with them making the default a snap - as I said, sandboxing a browser probably is a good idea from a security perspective, and most people probably aren’t going to care about snap vs. deb installs, so why not go with the safer alternative?

My issue was that it kept switching back to snaps even after I tried to go to .deb installations. It happened at least three or four times. It would be fine for several months, then something would happen during an update, and it would switch back.

I didn’t have the concerns the article mentions about it automatically updating; it would only update whenever I told software in general to update.

I can’t find it at the moment, but a few weeks ago I made a comment that I didn’t really care for the paddle shifters in our car (it’s an automatic, but you can switch to “manual mode” and shift it manually), because I know it’s not going to let me do something stupid, whereas a stick shift will usually let me do stupid things that can damage the engine. That’s partially what prompted the measuring power as ability to screw things up comment. :)

You know, I assumed Canonical was pulling something, but it’s possible it was also just incompetence. I didn’t think they even distributed a .deb version of Firefox, so it definitely felt like they WANTED me to use snap Firefox…and then I’d start wondering why it was so important. What vested interest would Canonical have in me using snap Firefox? Maybe it was just honest mistakes.

Linux is about freedom to make our own choices, and whatever is happening with Canonical (malice or ineptitude) was getting away from that. Kubuntu feels like, “We’ve made this garden for you and we recommend you stay inside it.” Debian feels like, “Hey, man, you wanna go hose your system? Here’s the apt command to do that. Have a good day.” (Apparently, I measure true power as ability to screw things up.)

Slackware: “You have all of the power. Right now. And all of the responsibility.”

I just switched away from Kubuntu to Debian.

The snap thing was annoying, but not a major problem for me, except for one thing: I switched Firefox back to a debian package, following the directions online to do so, and every few months it seemed somehow I had been switched back to a snap version. I removed the snap and all of that, but every now and then I’d realize I was using Firefox in a snap. (It became obvious when I tried to unlock 1Password - the snap version relies on the plugin, but the non-snap version fires up the standalone 1Password program.)

In general, I’m not opposed to the concept of snaps, and a browser is probably something that should be in a sandbox. But, I preferred the standard Debian package installation, and somehow that kept getting overridden. And that is the kind of thing that I hate about Windows.

The install was smooth, or would have been if I hadn’t had a slightly unusual setup with my drives. It works just like Kubuntu, by switching to KDE with X11 (I had a few minor issues with Wayland), but without Canonical. I don’t need bleeding edge, I just want my system to work reliably.

My Linux background: Spent a lot of time with Slackware starting in the late 90s, both on server and desktop. Switched desktop and laptop to Kubuntu around 2010. Server got switched to Debian in 2017 or so.

I think, for me, the proverbial straw was the Unifi controller. I was just like, “No. I can’t do this. I don’t want to do this.” My desktop was running Kubuntu at the time, so installing it on there temporarily was a breeze (confirming I was making the right choice), until I got the server switched to Debian.

Whoa. So I grew up on Slackware but switched to Debian some time ago, and I can say I’m MUCH happier on Debian. The dependency hell on Slackware just killed it for me. I know they have some management of it now, but I just couldn’t take it any more - I was spending way more time administering the machine. I held my breath updating, which made me reluctant to update, which isn’t a good thing from a security point of view…

I’m starting to think this really is it, because it again worked while I was away eating lunch - it turned off my monitor that is hooked to the Intel integrated video. The other monitor is currently switched to my work laptop.

Thanks. That gives me something to look into. Wonder why it didn’t happen under Kubuntu…I kept it up to date, but it still might have been too old in some way (X11 instead of Wayland or something).

Interesting. I’ll try the kscreen2 kill again.

Interesting, but I haven’t changed that either.

And, gah, it just worked normally. WTF. I haven’t changed anything yet this morning.