Tell me you’re a novice without telling me you’re a novice.

Edit replacing my original comment:

Looks like that package has been superseded by org.gtk.Gtk3theme.Breeze. That’s what I’m using, and it is receiving updates.

$ flatpak remote-info flathub org.gtk.Gtk3theme.Breeze-Dark
         ID: org.gtk.Gtk3theme.Breeze-Dark
        Ref: runtime/org.gtk.Gtk3theme.Breeze-Dark/x86_64/3.22
       Arch: x86_64
     Branch: 3.22
 Collection: org.flathub.Stable
   Download: 156.9 kB
  Installed: 386.6 kB

     Commit: 5a19b0c0808f82290d1f64c95d2406a860329817e0f269b4aaf0a1bbba92323a
     Parent: 390f820d32df2f22e3a3165eb4d65071dcb93a357ae7730f4ca548b5d016b966
End-of-life: This theme has been replaced by org.gtk.Gtk3theme.Breeze, see README for workaround on using system color schemes. https://github.com/flathub/org.gtk.Gtk3theme.Breeze#workarounds
    Subject: Add EOL (fc4339ff)
       Date: 2022-02-22 00:21:51 +0000

Wildermyth is a lovely combination of storytelling and xcom-style combat, with a genealogy system and chances for your heroes (and their descendants) to reappear in future games.

I think that was sometimes true in the past, but they ended that practice years ago.

KDE Connect also runs on more operating systems. It’s worth mentioning to friends who run Windows.

It’s a time-honored tradition among dictionary publishers.

Do you have the xdg-desktop-portal-kde package installed?

OEM support for the device is needed because an alternate OS cannot provide firmware updates otherwise.

Firmware and drivers can be made open, just as other software can be made open. It’s really just a matter of incentives. In my experience, law tends to be a pretty effective incentive.

If the bill of materials included the legal requirements discussed here, then a component supplier would either start producing open firmware/specs, or they would lose that market to another supplier.

Obviously, Android would not be the only project/product affected by such a legal change.

6 ≠ 16
v ≠ o

and your only option is to drop another couple grand for a whole new device

…and send another whole system into the waste stream. It’s incredibly irresponsible.

On the other hand, I can put an open OS on my Android and get security updates long after the manufacturer has abandoned it. Can’t do that with an iPhone. (But honestly, few Android devices make it easy, and none that I know of allow every little part of the system to be supported this way.)

It’s about time we started legally requiring manufacturers to unlock our hardware when support ends, and release the driver specs ahead of time, so the open software community can take over support. The unending accumulation of e-waste due to nothing more than abandoned software is unforgivable.

This goes hand-in-hand with the right to repair.

I imagine the reasons include convenience (for the ISP) and the possibility of upselling.

There is at least one advantage to customers: address rotation makes it harder for third parties to track you.

Alt+Wheel works for me. Plasma 5.27.5, Qt 5.15.8, Okular 22.12.3.

Is it possible you have overridden the default shortcuts, or something is interfering with them?

Do you have an unusual mouse wheel, like one that rolls freely instead of in steps, or a touchpad-simulated one?

Maybe you’ve discovered a Plasma 6 bug?

Yes, Alt+Wheel normally works. I think it’s a standard shortcut in Qt apps. (Gtk apps use Shift+Wheel.)

This assumes you’re not in Fit Width or Fit Page mode, of course.

Because it’s the foundation of a lot of cross-platform code, from the standard libraries in various programming languages to innumerable shell scripts.

Unless all the computing devices you use run Windows, you probably depend on POSIX, whether you have direct contact with it or not.

Yes.

Another thought: Is it possible that your original user account (which hangs) is trying to log in to an X session while the new one (which works) is using a Wayland session, or vice-versa? That might explain the difference in behavior if only one of the two session types is broken.

Good luck!

I use KDE on Debian. I have not encountered this, nor can I think of a reason why showkey would break a user’s desktop session.

If the GUI login screen is still visible when it hangs, I suppose sddm might be having trouble. To investigate, I would run journalctl -f in a text console, and maybe tail -F /var/log/Xorg.0.log* in another, while attempting a GUI login. When it hangs, I would switch back to the text consoles and see if the most recent log messages hint at what’s hanging.

*(Or whichever log file corresponds to the new X session, assuming you’re using Xorg instead of Wayland.)

Could the fingerprint reader be causing the problem on the main account?

Reminds me of the Apple version of Karateka, which did something special if you inserted the floppy disk upside down.

https://www.theverge.com/2021/7/5/22564151/karateka-apple-ii-upside-down-easter-egg

Sadly, many motherboards don’t have POST code displays.