Wouldn’t this still be the superior solution? The article doesn’t mention the setup for using ROCm for cards running on amdgpu.

2-2-1 still insinuates having a remote backup. I don’t see how this particular threat destroys a 2-2-1 setup.

Use the OCI through podman or docker.

What compositor (desktop environment) and distro are you running for things to behave that poorly?

I have been utilizing BunkerWeb for some of my selfhost sites since it was bunkerized-nginx. It is indeed powerful and flexible, allowing multi-site proxying, hosting while allowing semi-flexible per-site security tweaks (some security options are forcibly global still, a limitation).

I use it on podman myself, and while it is generally great for having OWasp CRS, general traffic filtering targets and more built on top of nginx in a Docker container, the way Bunkerweb needs to be run hasn’t really remained stable between versions. Throughout several version upgrades, there have been be severe breaking changes that will require reading the setup documentation again to get the new version functional.

As the original issues over on MySQL forums suggested, using DBeaver or other similar software rather than SQL Workbench is the best option. You unfortunately seem to be locked into using a keychain solution if you want to use SQL Workbench.

Perhaps it is possible that multiple issues are involved? Looking back at other issues with SQL Workbench causing DBus failures due to missing DBus endpoints could include the fact that SQL Workbench seems to rely on a keyring (be it Gnome Keyring or KDE Wallet). In an issue posted from 2022, SQL Workbench outright fails to connect to DBs in the same manner described if the keyring application isn’t running. It might be worth using KWalletManager to check through your KDE keyring to see if SQL Workbench has been attempting to store and resolve database passwords through your keyring, which won’t be running by default in a plain i3 session.

Traditionally, one using a “from-scratch” Linux install might start in a console TTY and then use the startx command to start X.org and other applications alongside it (including the window manager like i3). This is often done through the .xinitrc file. In your case, it’s likely that you aren’t using such a method, and rather using a display manager (most likely sddm since you are using KDE Plasma) to launch your user session (a bit of an oversight on my part, my bad). When not having some kind of pre-launch file or some other service list to launch everything surrounding your desktop, you might have to rely on your window manager to ensure secondary processes are launched. I do believe sddm can be configured to allow for additional processes to be launched, but I’ll point you in the direction of doing it from i3’s config files as it’s quite simple to do.

Within your i3 config file, you can add exec entries into it. Typically exec entries are meant to be used with bindsym to launch things with a keybind, but you can use exec entries on their own line to launch applications when the configuration file is read (on startup). For instance, you could add the line exec --no-startup-id "/usr/lib/polkit-kde-authentication-agent-1 &" in order to launch KDE’s polkit authentication agent with your i3 instance, at which point applications (like SQL Workbench) should be able to make use of. As usual, changing your i3 config does require restarting your session for changes to take effect.

So you executed KDE’s auth agent in a terminal and then ran the mysql service through the same terminal and everything worked? If so, that’s good. I believe the only thing missing to getting SQL Workbench working is by having your authorization agent of choice launched in your i3 .xinitrc file. That way it should initialize any environment variables for your full graphical session rather just for a single terminal.

Just a wild guess, but does your i3 setup have Polkit setup fully like it would be in KDE? The “the name is not activatable” is a string typically stemming from DBus. Especially for potential cross-user services that may require various permission sets, polkit is often utilized to bridge what is necessary. If you don’t have an authentication agent setup for your i3 desktop, you should probably set one up, even if it is something basic like xfce’s or lxqt’s.

User-Centric Innovation: Unveiling the Industry-Leading Battery Life

We know how a smartwatch becomes integral to its wearer’s life, and battery life can’t be a concern. That’s why we went back to the drawing board, driven by community feedback, to ensure the OnePlus Watch 2 delivers an exceptional user experience. With up to 100-hour battery life in full Smart Mode, it sets a new industry standard, ensuring that your watch keeps pace with your life, uninterrupted.

Really impressive how OnePlus is touting a relatively mediocre 4-day (at best) battery life on a smartwatch as something exceptional or something that they (falsely) claim as industry-leading. Maybe it is good by typical WearOS device standards, but is by no means top of the line for the smartwatch industry.

Not the same person, but I greatly enjoy my (now second) Pebble classic for several reasons, which I imagine some are shared between Starayo.

• Always-on Display
• Week-long battery life
• High contrast display that can be read easily in low light as well as in direct sunlight
• Simple notifications support, with quick canned replies
• physical button navigation that make the watch easy to use without needing to look at it
• Isn’t obscenely large
• quick launch application shortcuts from holding side buttons
• simple media playback control that is responsive
• Doesn’t attempt to be another smartphone, but rather as a local companion to your existing smartphone (doesn’t thrive on individual apps, but rather companion apps to complement smartphone usage)
• Customizable and relatively simple to write applications and watchfaces for.

Unfortunately for me, fossil’s watches do not match up. Looking at the gen 6, still uses an ill-suited AMOLED display that is bound to have poor contrast in direct sunlight unless the brightness is cranked so far that it will blow through the battery. Even then, the average battery life on the gen 6 is atrocious compared to most Pebble models as many reports say it can make it through one day. I’m sure by now, WearOS devices have worked out some of the kinks to make them easier and faster to use, though I am not sold on needing a personal assistant in order to do basic tasks (as Fossil markets their gen 6 smartwatch; I do doubt that this is necessary for general function).

Also, this might be controversial, but I personally feel that a device that has Bluetooth and is intended to communicate with a device that is often within ten feet of it really doesn’t need to waste resources and probably become more of a privacy nightmare by including Wi-Fi, LTE, and other data communication methods (beside NFC). Furthermore, pretty much every WearOS device I have seen has had a struggle to keep battery life for more than a couple days, and everyone deems that devices that can should be praised for whatever reason. Seeing as my ancient smartwatch that does most of what these newer watches do yet can effortlessly hold a six day battery life at worst, I seriously question why newer watches that have so much compromise and are incredibly misguided as to what a complementary wearable should be are what are being developed. Not to mention that the Pebble classic on launch was $99 USD whereas one can easily find $400+ smartwatches that still have way too much compromise in comparison.

There are not many Android phones that actually let you flex the open source benefits of AOSP. Android as it is packaged on many devices is not open source, and nor are the devices willing to fully let you install what you want. Ironically some of the only choices you have with the highest degree of freedom are from google.