Unable to browse after latest updates to tumblweed

That’s kind of exactly my point … why make “auto” different from what you’ve actually chosen with the checkmarks? Shouldn’t “auto” be “what it’s always done” … If I want to get fancy I’ll use zypper … anything much more than that is just gonna confuse newcomers … hell it already confused me

The checkmarks have nothing to do with it. It will still search in all the fields that you checked, but with the search mode that was detected (in “auto” mode) or that you explicitly selected in the combo box.

If I had hidden “auto” behind the combo box, most users would never discover it. Now it’s very prominent because it’s the default if you never changed it, and it also explicitly tells you that it defaults to “starts with” directly below the combo box.

Yes, that’s a change from the old YaST. I had chosen “contains” as the defaults many years ago, and I always regretted it when I used it; because it would typically find too many false positives. And as the author of the original code back 20+ years ago (yes, I’m old) I now took the liberty to change a bad default to a new one.

If we really want bug compatibility with the old thing, would you also want me to put the 50+ small and large bugs back in that had accumulated over the decades when some dozen different people who never understood the fine details of the code changed things and introduced all those bugs? Bugs like lists not being updated, details views not being updated, or displaying the wrong data? Qt signal / slot sequences totally screwed up? I don’t think so.

It’s a new piece of software now. Things change after several decades (!) of decay when the wreckers tear down the old cruft and build up new things that actually work. I know it’s hard to get over that; I’m an old guy myself. :wink:

1 Like

I would rather find false positives that weren’t checked than real positives that weren’t even shown

Strawman Argument

I very much doubt you’re older than me

Now that I understand what it is doing I can also understand the logic behind it … and if I hit package update it selects all the updates that do not need dup and then I can see those that do which I like. This has helped identify network packages recently which have screwed up.

NOW I just need to know how to get it to display using the system font rather than something almost too small to read! I’ve been forced back onto wayland since X11 is now not allowing me to reduce the global size setting at all, but in wayland the start bar is half off the bottom of the screen ALL of this is just a complete mess when we had a working display system.

KDE wallet strikes again lmao, I have helped multiple people with this issue, sometimes KDE wallet will open on another desktop and they won’t notice.

My advice:

If you are not actually using “pam_kwallet” then:

  • uninstall pam_kwallet
  • taboo pam_kwallet so that it is never automatically installed.
1 Like

Remember that you are normally running Myrlyn as root, so you have to do any font changes in the root user’s desktop. The easiest way is to log in as root for once, change the font there, log out and log back in as yourself.

I described this procedure and also alternatives in detail for my (also Qt-based) QDirStat here.

HTH

1 Like

shundhammer
Thanks for that … That was the exact poke I needed to realise how to fix the bigger problems. The problem however seems to depend on just how you log into ‘root’ as X11 and wayland screw up different things. I have created a new user account and while a few things no longer work, I’m using wayland and many of the ‘complaints’ about it have evaporated perhaps helped by the fact I have a crib sheet of changes to get other apps displaying properly. myrlyn is displaying in a better fiont size, but I STILL have problems with pop-up windows remaining in an almost unusable size :frowning: