• 4 Posts
  • 10 Comments
Joined 1 year ago
cake
Cake day: June 7th, 2023

help-circle




  • Yes, I think the card is the weak point here or better the weak driver support. My next laptop will definitely have a AMD card. But I have absolutely no idea which one is good enough to handle actual games with full details and usable fps. I don’t expect Desktop like experience but at least 40 fps with full details in an actual game would be fine. Im not a professional gamer, but when I have the time to play, it should be fun and not frustrating. Mostly I do coding with VSCode and some database stuff in different flavors. So a not to small display is a must have.

    Can you recommend a good GPU? For the rest I can do my own research…





  • That window titles can be easily changed is quite true, so all applications I know monitor such changes and abort the autotype on request when a change is made. But as already said, this is not a security feature, at least not a useful one.

    Monitoring the application itself makes no sense for a password manager. As you write yourself, it’s easy to customize the title. All applications make use of this. It is already changed when the tab in the browser changes, a new page is loaded or similar. The same is true for non-browser applications. Windows also allows read access to window titles.

    What the Wayland developers do is, in my opinion, gross mischief or ignorance regarding window titles. The password manager needs a simple way to assign a window to an entry, which should be the same for all applications. This should be the same for all DE’s, window managers and OS. The simplest is the window title. The status bar makes no sense and an API would have to be the same or at least similar across all DE’s, window managers and OS. Such a thing does not exist. To implement something like that only for KDE is too niche. This would have to be implemented and established, if already for the broad mass. So also for Gnome, Mate, Cinnamon and all the others. Not to forget, this must also work for Windows and MacOS in a similar way.


  • This is because Wayland doesn’t allow it to read window titles. Keepass and KeepassXC uses the window title to identify which entry to use. If you have no title, you can’t find the entry. That’s why it will not work with Wayland and never will work, until Wayland allows it to read window titles.

    XWayland, which is forced with your workaround, is not Wayland.

    That’s at least for me, the main reason not to switch to Wayland. I have no idea why Wayland doesn’t allow reading window titles. There is absolutely no security or performance benefit of this behavior. For me it’s either a bug or a design failure. Or simply bad behavior.


  • Not really. In my case i start it from within Steam Library and not from commandline, but i have tried the --force -q dotnet48 shortcut also, with no positive result. Yesterday, I could play the game for more than 3 hours, but today, starting it the same way, it crashes after loading 1% of the save game.

    I’m starting it now in a parallel installed Windows, where the save game location is shared between both OS (-appdata "/path/to/folder" -skipintro). Maybe i find a better way and must not boot to Windows. Since i start this really seldom, it has to download a lot of Updates before i can continue.