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

help-circle

  • According to the linked wiki, try to go to https://nouveau.freedesktop.org/CodeNames.html.

    Check on your laptop with dmesg | grep -i chipset the codename of your graphic card. With this you can check which driver is the best on https://wiki.archlinux.org/title/NVIDIA. There is a paragraph, explaining which driver is the best.

    If I understand it right, the nvidia package is the correct one for 1050. So you can use pacman -S nvidia with root privileges. All dependencies should be resolved automatically.

    I would recommend to reboot, in case there are changed kernel modules.

    2 things i have to note: Using Wayland is a total mess with nvidia. Specially on Arch Linux. I have screen flickering in GUI and games, the performance is so lala and tools like KeePass which needs access to the text in window titles did not work complete. On Manjaro, the flickering doesn’t exist, but the other symptoms do. Maybe im missing some packages on Arch.

    Second with Vulkan i have some tearing in games. I have not looked further in to that.

    On the other hand, games like Satisfactory or Elder Scrolls Online, have more FPS with the same settings as on Windows.

    Currently i test Arch and Manjaro in parallel on the same Laptop. But I tend to keep Manjaro and remove Arch. There are light pro’s and con’s, but overall, I’m more happy with Manjaro. But this has nothing to do with you’re issue.




  • df -h

    Manjaro:

    dev             7,8G       0  7,8G    0% /dev
    run             7,8G    1,9M  7,8G    1% /run
    /dev/sdb3        68G     50G   15G   78% /
    tmpfs           7,8G       0  7,8G    0% /dev/shm
    tmpfs           7,8G    9,0M  7,8G    1% /tmp
    /dev/sdb4       587G    272G  285G   49% /mnt/games
    /dev/sda1       296M     56M  241M   19% /boot/efi
    tmpfs           1,6G    100K  1,6G    1% /run/user/1000
    

    Arch:

    dev             7,8G       0  7,8G    0% /dev
    run             7,8G    1,7M  7,8G    1% /run
    efivarfs        128K     46K   78K   38% /sys/firmware/efi/efivars
    /dev/sdb5        69G     21G   45G   32% /
    tmpfs           7,8G       0  7,8G    0% /dev/shm
    tmpfs           7,8G    8,6M  7,8G    1% /tmp
    /dev/sdb4       587G    272G  285G   49% /mnt/games
    /dev/sda1       296M     56M  241M   19% /boot/efi
    tmpfs           1,6G    108K  1,6G    1% /run/user/1000
    /dev/sdb2       1,2T    796G  332G   71% /mnt/volume
    



  • Keep a minimum of 30GB free, for Windows update processes on the windows system partition. I don’t how much the windows installation counts in space, but add that to the 30gb free space. I would recommend to have a extra partition for the games on NTFS and move your steam, epic, ubisoft, whatever library to that partition.

    I have tried to use the same gaming partition between Linux and Windows, but failed every time. In the worst case this can alter your Windows privileges. At least I had this issue.

    Currently I’m using Windows only for 2 games: Space Engineers and Empyrion. The rest works with better performance on Linux. Satisfactory, Ark survival, Elder Scrolls Online have more FPS on Linux with the same settings. I have to use a nvidia 1050 Ti in my laptop. With a AMD GPU the situation is a lot better on Linux.

    I’m not a hardcore gamer, mostly im coding here and there. But sometimes gaming is a must have.







  • 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…




  • From my point of view, this is all relatively unstable and not really well thought out, far from being reliable. I have spent the last 2 weeks trying to convert my Crossbowser bookmark backend (https://codeberg.org/Offerel/SyncMarks-Webapp) into a functioning PWA. Very disappointing. Don’t ask me how many nerves I’ve lost in the process. At least you can now use the WebApp as a PWA. The share_target also works if it was installed via Chrome or Samsung Internet. It also works offline. These functions are even retained if you subsequently uninstall Chrome/Samsung Internet. The WebApp then asks which browser wants to take over the functions. This also works with Chromite or Firefox. Strange but what the heck. At least you can now share any URLs with the backend. This also works offline, even if this is more of an Edge case for bookmarks.


  • Oh there is a APK, when using Chrome or Samsung Internet (installed via Samsung Store). The store is generating and signing the APK. Only with such a signed APK OS Level functions will work. A good example is the share_target functionality. If this is enabled by the PWA and installed as APK, you can share text and links with the PWA. The same applies for PWAs on the Desktop, for example with Edge on Windows.

    If you use the same PWA with Firefox or Samsung Internet installed from Play Store, it can only add a shortcut on the home screen, without share_target functionality.

    Additionally some service worker functionality is very basic on some browsers. On one hand this is bad for functionality, but good for privacy. Assume a PWA uses a background sync service for example. This can exchange a lot data and sync it with any target in the web, without user consent. This is only a small part where service workers do not respect users privacy.

    If you look at that we come in fast steps to this insane and total crazy manifest v3 webextensions. They are completely privacy nightmare at least how Chromium designed them. The Mozilla implementation is a lot better, but incompatible to Chromium.

    Welcome to the ugly world of new web technologies.







  • Yes, that’s my understanding of xdg. But I have no idea what this means for Ungoogled Chromium package. Base Chromium itself isn’t degoogled. It has most of the Google service’s active and enabled. Only a minor subset, like bookmark sync is disabled (but technically available). With Ungoogled Chromium, most (not all) Google dependencies are patched and inactive. At least this was the case as I last checked it. Since I prefer a mostly Google free environment, I would like to use Ungoogled Chromium for testing and a patched Firefox browser for standard web things.




  • 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.