• 211 Posts
  • 81 Comments
Joined 1 year ago
cake
Cake day: July 28th, 2023

help-circle






























  • From the Discourse Blog:

    The Linux desktop provides XDG Desktop Portals as a standardised way for applications to access resources that are outside of the sandbox. Applications that have been updated to use XDG Desktop Portals will continue to use them. Prompting is not intended to replace XDG Desktop Portals but to complement them by providing the desktop an alternative way to ask the user for permission. Either when an application has not been updated to use XDG Desktop Portals, or when it makes access requests not covered by XDG Desktop Portals.

    Since prompting works at the syscall level, it does not require an application’s awareness or cooperation to work and extends the set of applications that can be run inside of a sandbox, allowing for a safer desktop. It is designed to enable desktop applications to take full advantage of snap packaging that might otherwise require classic confinement.

    So this looks like it complements and not replaces the XDG Desktop Portals, especially for applications that have not implemented the Portals. It allows you to still run those applications in confinement while providing some more granular access controls.






  • Depends on your perspective, I guess. To me, GNOME is now pretty mature, stable, and reliable. That is one of the reasons why I left Pop-shell for a more vanilla GNOME experience.

    COSMIC has a lot of hype right now, but based on my experience (and others), it is not at all stable or ready as daily driver. That is not to say it isn’t exciting but at this point in time I value stability and being able to just use my computer and GNOME provides that.

    As the Linux luddites used to say, not all change is progress :)



  • This reddit post seems relevant. A user mentions:

    I found out that only the containers having these kind of networking problems where all running the container in “host” networking mode.https://docs.docker.com/network/drivers/

    Since I don’t need host mode, I can just comment that line out, and it will start using the standard Bridge (which will be used by default if you don’t specify any networking settings for your containers)

    This is running under docker as you had in your initial configuration.

    Another reddit post mentions setting the gateway and DNS server if you have a static IP:

    It turned out to be nothing to do with Plex but rather was the fact that there was missing information on my static IP setup. Once I added in the gateway and DNS information those extraneous messages went away.

    I’m not sure if that will help, but it’s perhaps something you could consider as you debug this issue. Good luck.