• 4 Posts
  • 120 Comments
Joined 1 year ago
cake
Cake day: March 14th, 2024

help-circle


  • I know that OP already found the solution but I just wanted to chime in because every person who commented completely misunderstood the question. It’s normal that some extenions don’t support the new version after updating GNOME but in that case, the switch will be disabled and it will show you a warning that the extensions doesn’t support the new GNOME version. OP clearly stated that they could still switch the extensions on and off. Besides that, most extensions will already have been updated to support the new version by the time the Fedora update comes out, so it wouldn’t make sense that all the extensions wouldn’t work anymore.

    As a tip, you can install “Extension Manager” instead of the default “Extenions” app and besides being able to install extensions right through the app, it also has an “Upgrade Assistant” function, which lets you check which of your extensions support the GNOME version you specify. That way you can check if your extensions will work in the new GNOME version before updating.








  • Fisch@discuss.tchncs.detoOpen Source@lemmy.mlGIMP 3.0 Released
    link
    fedilink
    English
    arrow-up
    26
    ·
    4 months ago

    Idk if GIMP has a marketing problem but I definitely agree that FOSS projects should add screenshots and a description of what the program does to their website and repo. It really annoys me when someone links a piece of software and it just doesn’t say what it does and there’s no screenshots that would make it easy for me to see what it looks like and how the UI is structured. When there’s no screenshots I’m rarely even interested in trying it out because, even with a description, I don’t really know what it is. Like, I wouldn’t be interested in a car based on only a description, I’d have to see a picture of it too.








  • Fisch@discuss.tchncs.detoLinux@lemmy.ml...
    link
    fedilink
    English
    arrow-up
    39
    ·
    edit-2
    5 months ago

    What this person told you was wrong, you need to use flatpak run [package id] to run flatpak apps. You can do flatpak list to see all installed flatpaks with their ids. An id looks something like org.example.app and you’d run it with flatpak run org.example.app.

    Also, is it shown as being installed in Discover? If it’s not you could try just installing it again and if it is, you can try uninstalling it first. The user data for Firefox should stay intact.