• 0 Posts
  • 236 Comments
Joined 2 years ago
cake
Cake day: March 22nd, 2024

help-circle



  • The largest one is probably the lack of churn. I don’t have to relearn what things look like or how controls function every few years (or where settings have migrated to, or how to accomplish random-obscure-thing-I-might-need-to-do-once-a-year). It lets me get on with whatever I sat down at the computer to do in the first place, which was almost certainly not tinkering with the DE.

    It’s also light on resources, since it dates to the days when a single core and 1GB RAM was considered a pretty decent system.

    (Note that TDE, which is what I am using, is still well-maintained—it’s just that the people working on it consider keeping the original look and feel to be one of their goals.)







  • In Firefox, I don’t remember having something similar. That was like 5+ years ago, I believe profiles were there, but perhaps less easy to use.

    The profiles feature in Firefox haa been there for a long, long time—more than a decade, and possibly longer than Chrome has existed—but not many people read the documentation to find the command-line switch to evoke the selector, and they’ve never been terribly easy to find from inside the GUI.











  • That sounds like bad data got written to some config files, because a reboot should have corrected a simple bad handoff and restored the preconfigured state. Might have been interesting to see what xrandr had to say about those monitors at the time, and whether it could have fixed them.

    Anyway, sounds like your side monitors got disabled, and rather than re-enabling them when you exited WINE, something in the stack decided they’d always been that way . . . but because they were still powered and connected, the monitors still said “hi” every few minutes, and then got identified and swatted down again. I doubt I would have had the hand-speed to re-enable them through the GUI the way you did.