EDIT

So anything I said below was all a lie, it turns out that the issue was kde and my monitors, which are 240hz. I swapped to gnome and the issue disappeared, and then I installed bazzite kde on a second drive and the issue reappeared. Setting my refresh rate to 120hz stopped the flickering and upon setting it back to 240hz I do notice an appreciable decrease in artifacting. I have no idea what to do with this information, but if anyone is experiencing this try just decreasing your refresh rate for your monitors.

Howdy,

Just installed Nobara again and am trying to figure out why this is happening. I think it’s a firefox thing since I haven’t seen it happen in any other application; basically anytime I do a lot of scrolling, the firefox window breaks down and I can see my desktop background behind it. It always happens in the bottom right cornerish part of the window. I’m up to date on all updates as far as I’m aware. I did some googling and checking out the nobara discord but I couldn’t find anything related. I tried recording my screen via spectacle to show the issue, but it wouldn’t capture the issue.

Any help would be appreciated; I am a linux beginner so dumbing down any info you have would be nice. Thanks!

  • ferric_carcinization@lemmy.mlEnglish
    7·
    2 days ago

    There are a few common ways to distribute software for Linux, which I’ll try to explain while leaving out the more complicated parts:

    • Appimage: The program & all of its dependencies are put into a special filesystem image file. (think special .iso or .zipfile) Works on any distro & does not require administrator privileges, but has a large file size. This is somewhat close to an .exe file.
    • Statically compiled binary: The program is compiled in such a way, that the program file contains all dependencies. Unlike an appimage, the program file is not an archive, so it does not contain any files within itself. So, all the libraries (small program parts) are placed in a large program instead of being zipped up. Can usually be run without proper installation, like appimage & .exe files. This is also a bit like an .exe file.
    • Package: The program & asset files are archived, usually compressed .tar archives, (linux equivalent of .zip/.7z/.rar) which are extracted (unzipped) during installation. Sometimes a small included script is run during install/update/removal. Usually, architecture (x86, ARM, risc-V, etc.) & dependency information is also included. Common package formats include: .deb (Debian based distributions like Ubuntu, Mint, etc.), .rpm (RHEL, OpenSUSE, Fedora & derivatives). These packages are usually somewhat distribution & version specific. For example, you might be able to install a Debian .deb on Ubuntu, but if you have incorrect versions of dependencies, it either cannot be installed (you get a warning/error) or the program won’t work correctly or at all. Often, package managers like apt, dnf & pacman get these for you, so you don’t need to think of them as files, but you can also install package files like .deb or .rpm.
    • Flatpak: This one’s a bit complicated. Something of a mix of all of the above. Works anywhere, but you need to have the application flatpak installed to run programs installed this way. Flatpak programs are installed for each user, meaning that no administrator privileges are required. They also support sandboxing, meaning that a program only gets access to files & functionalities it needs, like on smartphones, but that is optional and not all programs make use of it.
    • Snap: Also complicated. For an average user, mostly like flatpak. Only guaranteed to work on Ubuntu, but might work elsewhere.

    So, how you installed a program may change how it works a bit. For example, the versions of dependencies you have can change the program’s behaviour. Also, some configuration can often be done when compiling a program, like specifying whether to use Qt or GTK for drawing windows, or disabling bluetooth support. Different packagers (people who make appimages, flatpaks and/or paclage files) may choose different options here.

    Sometimes flatpak programs may use old versions of dependencies. Also, I’m not sure if this is the case with Firefox, but Chromium’s (Google chrome & derivatives, like Brave) sandboxing (security things) conflict with flatpak’s own, so some of Chromium’s security features are disabled in favor of using flatpak’s own ones.

    If the flatpak version of Firefox caused issues, I’d recommend trying the native version (package manager) instead of one downloaded from the internet. You can either do this from the graphical app store by selecting something like native, dnf or rpm instead of flatpak, or the native package manager with sudo dnf install firefox for Nobara, I think. Unlike flatpaks, native programs are installed for all users & require you to type your password during installation.

    If you use an appimage or manually downloaded .rpm file, you need to take care of updates manually, by downloading a newer version like you did during installation. I would strongly advise against this, unless necessary & you know exactly what you’re doing.

    I think this answered your question, but feel free to ask if anything was unclear or you have other questions. I’m a programmer & I’ve used Linux for a while, so I should be able to answer most questions.

    Edit:
    Sorry for the wall of text. I hope it wasn’t too jargony.

    TL;DR:
    The wall of text has context & things that might br good to keep in mind, but I’d recommend removing the flatpak version & the Linux .exe equivalent you’re using, then trying sudo dnf install firefox.

    Edit 2:
    Nvidia can sometimes cause problems on Linux, but if a different version of Firefox worked, it is very likely not the case here. Sometimes switching from Wayland to X11 or vice versa might help a bit, at least until the next driver update. Otherwise, I’d recommend Wayland, as it’s more secure, actively developed, has fancy features X11 lacks & can be a bit more efficient.

    Glad you found a way around the problem!

    • Valencia@sh.itjust.worksOP
      4·
      2 days ago

      Thanks for the response, definitely helpful! My follow up to that would be I’m still not sure how updating would work if I run the command you posted. Once I run that in the terminal, how do I know when there is an update for firefox? Will firefox just tell me like in windows, and update itself? Do I need to run a specific command in the terminal to prompt updates?

      While I have you here too, I’ve just found one more bug that’s been bothering me… In the application launcher, when I try to use the scroll bar the cursor won’t select the bar itself, instead just defaulting to resizing the window. Any ideas on that? It’s kind of a pain but I could live with it. Googling again didn’t really bring up anything conclusive. Here’s a clip to see what I’m talking about. Thank you again!

      • ferric_carcinization@lemmy.mlEnglish
        4·
        2 days ago

        If the grahical app store has asked for a password when updating, like on normal Fedora (what Nobara is based on), all programs installed with sudo dnf install <program(s)> are also updated. A update to native packages can also be ran with sudo dnf upgrade. Flatpaks can be updated from the app store or with flatpak update. (no sudo, as that just raises the privileges for the next command, like dnf)

        Linux has become more user-friendly, but due to the many, many alternatives for pretty much everything, while some programs integrate well with each other, this is not the case for everything, sadly.

        Sorry, I don’t know about the scroll issue. The scroll wheel on a mouse or dragging 2 fingers on a touchpad should still work.

        TL;DR:
        If you are prompted for a password when updating, everything’s fine. This should be the case for you, as Nobara is based on Fedora, which supports this. Otherwise, you have to run sudo dnf upgrade or the equivalent for your distributions’s package manager.