What was wrong with the old logo¿?

No Xorg also ships with up to date distros like Debian, arch, Ubuntu, etc but several of them have switched to using Wayland by default. It is deprecated because it is no longer actively developed and only maintained by a small group of devs and even that because these devs work for companies like Red Hat, Oracle, etc who have a vested interest in fixing those bugs

So I am guessing that always on top works on the flatpak version because it is running through XWayland

Thanks

What bling¿? I thought endeavorOS was very minimalist as well. Just arch with an easier installer

Thank you. Cool people like you are the reason why morons like me are able daily drive linux

Thanks for the correction. I will report the bug

Is it supposed to replace the % with %%? Because that is what it seemed like it should do from the code.

If this is the bug you are alluding to then i will report the bug or else please tell me what the bug you referring to so i can report the correct thing

Nevemind I figured it out. Was trying to give a new drive read write access for backups and the error stemmed from the fact the name had a ℅ in it.

Edit - It was the path to the folder not the drive with had %

With something like dash to dock or dash to panel, you get extra functionality while still retaining the stock workflow of gnome. I myself use near vanilla gnome with dash to dock, clipboard indicator and gsconnect. Out of those only dash to dock modifies the workflow but in a way that supplements the stock workflow.

They are usable but nowhere as good as gnome’s implementation. Fortunately this seems to be improving with plasma 6. One of the devs inspired by gnome has implemented gnome-like swipe gestures and a similar workspaces overview

This is Top tier sarcasm!

First of all, talking about a photon’s experience is weird because when moving at the the speed of light, the transformation equations associated with changing the frame of reference start having infinities appearing within them which makes it impossible to mathematically define things like time elapsed or distance travelled.

Secondly it is a little confusing to talk about of frames of reference but I will try my best to explain.

Assume there are two balls(A and B) in an empty region of spacing moving away from each other at speed of 1m/s. Since there are refrences in the background, we have no idea of both the balls are moving or ball A is the only one moving or ball B is the only one moving. From ball A’s perspective, it would seem like ball B is moving away from it while it is stationary. Vice versa for ball B which thinks A is moving while it is stationary. Now let us say that the balls have a way to measure the time elapsed and distance travelled. Now when ball A sees that 10 seconds have passed and that ball B has travelled 10m. To verify this it measures the reading shown by ball B. To its surprise it finds out the reading from B’s instruments show that only 8 seconds have and that B travelled only 8m. This is the time dialation and length contraction that happens in special relativity. Till now everything is fine but interesting things start to happen when you switch perspectives. In the frame of reference of B, it measures that 10 seconds has passed and that A has moved 10m in that duration. When it tries to verify these measurements from A’s instruments, it finds out that they show that only 8sec have passed and that A has only travelled 8m. Now we are in trouble as these measurements seem incompatible. Not only are the instruments not agreeing with each, other, the instruments don’t even agree with themselves depending on the frame. This is eventually resolved by the realisation that the order of events is not the same for all frames. In A’s, frame, it seems to B that started measuring late by 2s while from B’s frame it seems A started measurements later. Adding this 2 second delay in both frames solves all the measurement inconsistency issues.(The numbers used are random. If you actually calculate the difference in measurements coming from a relative velocity of 1m/s, the differences will be exceeding small)

Now that a basic understanding is out of the way, let us discuss the case of the photon. From our frame of reference, the photon is moving at the speed of light, we can measure with our instruments for how long the photon moved and what was the distance it moved but when we measure using the photon’s instruments we see that the clock always shows the same time and no time has lapsed. From the photon’s frame, it seems like it is stationary and everything else is moving at the speed of(which is obviously not true. Weird things happen when we try talk of moving at the speed of light beacuse of the infinities I aluded to before) and so while it clock is ticking, the clocks of the world around it seem stopped. So in conclusion while it valid to say that photons experience no time, it is only because we can’t go to the photon’s frame of reference because physics and math fail us that point.

Sorry for the incredibly long reply.

Actually light does experience time in its own frame of reference. For somebody observing(us in this example) the light or any object that moves at the speed of light in vacuum, it would seem that object is not experiencing time at all, that is, if there was clock on the object and we tried to measure the time that clock reads, it would give the same number as the result of the reading irrespective of when or where we measure it in our frame of reference.

I’m not sure if mobile AMD users have to do the same

No we don’t. Mesa and the kernel automatically decide to use the dGPU for intensive tasks. It is only on rare ocassions that I have to use the DRI_PRIME=1 to force the use of the dGPU. It has been months since I last did it

go mental like Torvalds.

What! I missed Linus going crazy¿? When did this happen¿? Do you have any videos¿?

But if you need the help of his code and products, then you should begrudging acknowledge that he is not an idiot. If you truly believe that he is an idiot, you should find a solution to your problem without pulseaudio or systemd because if not you are just an hypocrite.

DId your Nvidia drivers update recently? If yes try the older Nvidia driver

I have got an old shit laptop and I don’t see this. Can you verify this using mangohud¿?

Just for future reference.

KDE NEON is a distribution maintained by the kde community so that you can enjoy the latest and greatest kde has to offer on an Ubuntu base.

KDE plasma is a Desktop Environment(DE). It controls the look of your desktop and to some degree how you interact with your computer. You can use kde plasma in almost any distribution. It is somewhat analogous to launchers in android with the caveat that DEs affect a lot of more of the system than launchers do in android.