eldavi

i've been accused of that along with several other slurs like systems engineer and cloud operations engineer and it systems architecture analyst and software engineer. lol

i'm a software developer atm, but my current gig has a LOT of overlap with all of those other four letter word titles that i dare not repeat in decent company. lol

that dated comment was right and i hit that easy button five years ago. also i'm realizing now that doing so has completely removed me from the discourse that happens nowadays when it comes to gpu's and linux.

amd had already bought ati by the time i hit that easy button and that distinction that i used wasn't out of place at the last time i was paying attention and participating; or atleast wasn't so in my experience.

there used to be lists of rankings for compatibility for nvidia drivers and open source drivers as well. i wonder how i would go about finding the same for amd.

delete everything in /tmp; you're not really using it anyways and you'll get more disk space. lol

i literally used this same logic when i merged the contents of c:\windows & c:\win32 because there were so many duplicate files and folders and i needed to recover the free space.

sometimes i'm thankful for my cluelessness; examples like this paint me into corners and this particular corner was the impetus behind my exploration into linux; which has sustained my career for the last 25ish years through several once-in-a-lifetime economic recessions and multiple personal setbacks.

linux is the best mistake i've ever made.

when you use an xserver, it occupies one of those virtual terminals that i referenced in my last message.

most distros use 7 virtual terminals and the xserver is usually dedicated to one of them and that means you can use the keyboard shortcuts of alt+ctrl+f1 through alt+ctrl+f7 to switch from your xserver and into a bash prompt where you can then log in without the xserver and execute that command to look at the logs.

you can toggle between all 7 terminals at any time without impacting each other; you can use those keyboard shortcuts to help you troubleshoot this and all xserver problems in an "alt-tab" like fashion switching back and forth between the xserver and six other terminals where you can do things like execute commands; look at logs; & modify configs.

in your shoes: i would run journalctl -f to watch the logs scroll by on screen in one virtual terminal (whatever the systemd equivalent is nowadays; it was alt+ctrl+f1 through f7 back i the sysv-init days) and try to log in again on the base xserver virtual terminal and try to watch for errors/failures/warnings messages from that those scrolling logs.

journalctl is a unifiied logging system that comes with systemd so your logs are likely to persist there and it has built in tools to help you narrow it down if you see anything in the logs.

i'm going to assume that endeaveros is using systemd so you'll need journalctl and sudo at a minimum.

do you have access to both? as in can you run both commands?

use journalctl -f to show you what's happening as you try to connect and look for errors/failure/disconnects/etc.

thanks for explaining and i think i can understand your perspective.

if i understand you correctly: the lemmyverse has likewise made me weary and i had the realization that my paranoia of trolls where at an all time high because of the election.

i read through your post quickly the first time about because of that paranoia and made many assumptions based on my own experiences. as i said earlier; i haven't touched this area of my knowledge in several years and all of the questions always seemed to involve the word nvidia in the past and i assumed this was one of them.

i'm geniune in my effort to reach out and i think can prove it by trying to help: we need more information. Do you have access to the system's logs that would contain the package installation details?

i don't understand

my flatpak knowledge is malnourished; but looking at it from a high level containerization perspective, i would presume it depends on it the file system overlay is setup.

normally something like that would be defined in either the source image of the container or the mechanism used to modify that source image (eg dockerfile). if it's the latter it will be in the project's source and that source is probably on github. you should be able to search for terms in that source like "docker create" or "podman compose" to see how it's configured and use that has a starting point to search on something like google or openai.

this isn't an easy answer and i can go into lower level details; but your post contains a few key words like plasma and xdg-desktop-portal that says to me that you'll be able to figure it out how to make my advice actionable for your own specific situation if you think it applies and i hope that this lead pans out for you.

i tapped on the easy button the last time i wanted a new linux rig and bought a linux laptop from a linux company with its own os and its own paid developers and i've learned recently that it's made me unaware of the state of ATI and linux compatability vs nvidia's. what's your take on the state of affairs now?

i went with the easy button because of my experiences with nvidia and especially on my laptops; but my klutzy self has made getting a new one a necessity and i'm thinking that i'm going to go with AMD/ATI next time and do it the hard way like i used on a windows laptop; or maybe a mac.

i hit the easy button on my latest setup with a linux laptop from a linux manufacturer complete with its thier own OS with its own paid maintainers and reading your post reminded of the efforts like this that i don't do anymore because of that easy button.

it's been 5-ish years for me so bare with me while i try to catch up while we troubleshoot this together:

i'm unfamiliar with endeaverOS; is it a redhat or debian variant; which release/version?

what's the nvidia gpu model and are you planning on sticking with wayland and gnome?