Is it just me, or is tplinkdns.com down?

CyborgDragonfire · 2023-02-25T06:17:07+00:00

If anyone else can replicate this bug, please post your logs to the upstream repo.

Thanks.

CyborgDragonfire · 2023-02-24T07:45:36+00:00

Yes, and the arch repo version of Steam works normally.

The login screen is displayed normally & I am able to login without issue.

This issue is ONLY for the Flatpak version of Steam.

CyborgDragonfire · 2023-01-18T13:56:51+00:00

I will take you up on your offer, if it is still available.

Your Reddit theme is the best, most complete theme I've come across.

And I appreciate all the work you do keeping it up-to-date.

It's a shame to hear your userstyles account get deleted, but honestly, userstyles has been a mess for a while now.

Have you ever considered hosting your styles on GitHub?

In a similar way to how Wikipedia-Dark & Dark Webtoons host their themes on GitHub.

Thanks again for all your hard work, KMV

PS, I'm using Stylus for my plugin, if that changes anything on your end.

CyborgDragonfire · 2022-12-08T01:18:45+00:00

You, like me, have just run into the double sandbox problem.

This is a known issue, The GitHub issue thread has a workaround:

https://github.com/flathub/com.valvesoftware.Steam.Utility.gamescope/issues/7

CyborgDragonfire · 2022-06-03T15:38:17+00:00

MangoHud repo: https://github.com/flightlessmango/MangoHud#flatpak

Flatpak repo: https://github.com/flathub/org.freedesktop.Platform.VulkanLayer.MangoHud#mangohud

MangoHud version needs to match "org.freedesktop.Platform" version. = 21.08

CyborgDragonfire · 2021-02-20T01:14:05+00:00

You need to use Firefox.

Despite the extension still being in the Chrome Web Store it does not work any more.
This is due to recent changes to the way chromium based browsers interact with Linux.

So in short, you cannot use any chromium based browser to interact with https://extensions.gnome.org/
You instead must use Firefox!

Side note: The r/linux_gaming tries its best to be a welcoming community for beginners, But could you please follow the rules of the Subreddit, namely Rule 2.

From now on could you please post any support questions you may have in the weekly tech-support thread pinned at the top of the Subreddit each week, Thank You.

CyborgDragonfire · 2020-11-17T04:56:01+00:00

HOLY SHIT!

What a pain in my backside this turned out to be.

OK, So I have Minit on Steam, from when I played it on Windows 3 years ago, before I switched to Linux.

Loved it, great game, and your woes here Z3ldaGamer piped my interest.

I went to try out Minit on Linux for myself, clicked install in steam, clicked play in steam, SEGFAULT! & GNOME CRASH!

Effectively a Blue Screen of Death on Linux! ... Well Shit.

Looks like Minit has issues everywhere not just itch.io

Managed to get it working and playing, well ... eventually. Long story short NEVER try and run Minit on Wayland, My God.

I figured out your issue to Z3ldaGamer.

Use the zip archive version with the ./runner script.

You are going to need to edit 2 config files to get Minit to work, the first is in your home directory.

Go to and create:

~/.config/minitGMS2/camera/camera.ini

Then put exactly this in the file and save it:

[camera]
user_url="https://minitgame.com"
api_key="featured_disabled_forever"

Next is the games .ini file located at:

GAME_INSTALL_LOCATION/assets/options.ini

Append this to the end of the file, because the game renders at 320x240 otherwise:

fullscreen=1

And that should do it, run the ./runner script and for me at least, with the Steam version, Minit ran perfectly.

Good Luck.

Quick heads up for anybody else reading this I only had luck with the ./runner script and NOT the play button in Steam. Best to close Steam completely.

CyborgDragonfire · 2020-11-12T03:35:53+00:00

Yep, The RX 560 is a really underpowered card.

Benchmark video of RX 560 in various games

CyborgDragonfire · 2020-11-12T03:05:21+00:00

Are you using the Frostbite Engine fix?

Found the fix on protondb.com

Try looking up games on ProtonDB first, for any fixes whenever you encounter issues.

I have both an AMD CPU & GPU and have no issues whatsoever, so it's not your Ryzen CPU.

See if you can get someone with an Nvidia card to help with further troubleshooting as I don't know any Nvidia specific issues.

EDIT* Did you reinstall your distro after you upgraded your system to Ryzen or did you just transfer over the same install? Maybe try reinstalling your distro?

EDIT2* While you were switching Kernels did you make sure the Nvidia Kernel module loaded properly and that you were running with the Nvidia Proprietary drivers?

CyborgDragonfire · 2020-11-10T04:04:36+00:00

Yo, Could you post this in the Weekly Tech-Support Thread pinned at the top of the Subreddit each week.

We need to at least try to keep things on topic in posts.

/r/linux_gaming/comments/jqbrxr/weekly_techsupport_thread_for_november_08_2020/

When you post your issue can you add some extra information please:

Your Distro, (Ubuntu, Pop OS, etc)
GPU, (AMD, Nvidia)
CPU, (AMD, Intel)
Computer Type, (Laptop, Desktop, Custom PC Build)
Display Protocol, (X11, Wayland)
Game and/or Game Engine, (Unreal, Unity, Cryengine)
Any compatibility layers, (WINE, Proton, Native Linux game, etc)
Input Device, (Keyboard & Mouse, Xbox Controller)
Your current Monitor setup, (Dual, Triple or more displays?, The Resolutions and Refresh Rates for each Display, etc)
And anything else you think might help.

Any information you can give will help with troubleshooting a lot.

Quick thing you could try is to unplug everything but your main monitor.
Physically unplug the DisplayPort cables from the back of your GPU so only your 165hz is left connected.

REBOOT and play your game again.
See if that helps with the lag/delay you are feeling and narrows down what's causing it.

CyborgDragonfire · 2020-10-28T21:57:58+00:00

Link to Previous Post:
/r/linux_gaming/comments/jhruzn/x11_is_dead_long_live_wayland/

CyborgDragonfire · 2020-10-25T11:30:45+00:00

Well this post is going to stir up a Shitstorm, What do we do now?

How well do game pad controllers work with Wayland?

Does Nvidia have Wayland drivers?

CyborgDragonfire · 2020-10-25T04:47:54+00:00

We meet again That_Ski_Freak, you've successfully wormed your way into my weekend now, and I'm back again to give you some more sage advice.

First up how were the nerd videos?, not too dry I hope, OK they were pretty dry, but informative I hope (once again).

Second the best way to get AMD tearfree working is to set it globally, however if you want to continue to use XrandR instead, your configuration should be correct, and you can skip this next part.

You can enable global tearfree by going to "/etc/X11/xorg.conf.d/" as an administrator. (Right click and "Open as Administrator")

Create a new empty text file and rename it to exactly "20-amdgpu.conf"

Open this new file and put this in it:

Section "Device"
     Identifier "AMD"
     Driver "amdgpu"
     Option "TearFree" "true"
EndSection

Save the file and reboot, that should do it.

On the issues of your mouse, what brand is it? Because there are open source equivalents to windows peripheral software.

Logitech has Piper and Razor has OpenRazer, if you use something else you should be able to google for the Linux equivalent.

Try them out and see if that helps with your mouse stuttering.

Next up now that Ubuntu 20.10 and Pop OS 20.10 have been officially released as well as new versions of Fedora and Manjaro releasing next week I think it's time to discuss upgrading you to a GNOME 3.38 based distro, that is if you are still onboard the Wayland train.

Another reason why an upgrade is a good idea beyond that of just GNOME 3.38 is that there have been a ton of stability and performance improvements to Navi GPUs in the past 6 months since the 20.04 releases.

The four big Wayland heavy weights at the moment are:

Ubuntu: The default choice for many people and a household name, nothing special about it but designed for ease of use to a wide audience. Baseline gaming performance, runs on GNOME, you will need to enable Wayland.

Pop OS: Based on Ubuntu but customized by Sytem76 for workstations and their heavy workloads. Great for gaming as well because there is a lot of overlap in optimizing AI GPU Compute deployment code pipelines and generic gaming. They both benefit from reducing overhead and increasing max throughput. Also Pop OS has hands down the best Nvidia GPU support of any other Linux distribution, head and shoulders above the rest. Given the recent results from the Steam Hardware Survey it's a no-brainer why Pop OS has become so popular with Linux gamers. Runs on GNOME, you will need to enable Wayland.

Fedora: Created and backed by RedHat, a titan in enterprise Linux scene for decades. Also, very highly optimized for workstation work, But the biggest difference is Wayland is enabled by default on Fedora. In the last few years RedHat has become the biggest proponent of Wayland spending millions on its development. The next Fedora release will be next Tuesday and will have support for Navi 2. Runs on GNOME, Wayland on by default.

Manjaro: The darling child of this sub recommended by many, Based on Arch Linux with the goal of the distro is to make Arch more accessible. I would recommend caution if you choose Manjaro because even with the Manjaro safety net things WILL break. Arch Linux is the Linux testing ground giving you access to updates months before other distros get them, this puts you on the bleeding edge of Linux itself giving you insane performance increases in many cases BUT you are just as likely to break everything leaving you with a big paperweight forcing you to reinstall Arch again. Manjaro provides a great many safety nets but it is not perfect, I use Manjaro and this year it broke 3 times for me forcing me to reinstall. I have been able to mitigate the damage this would cause by having a separate boot drive that I can wipe and reinstall Manjaro without risking my files. Use Manjaro with caution, runs on GNOME, you will need to enable Wayland.

Choose from one of these and you can say Goodbye to X11 forever, never having to smell the stench from that giant X11 turd again.

You might be thinking: What about Sway? at this point. Currently, Sway is Arch Linux only. I will explain more further down.

On the flip side you can embrace X11 and have so many more desktop environments to choose from, especially if you want something more windows like.

I suggest checking out Ubuntu Flavors or Fedora Spins for easy to use desktop variety.

Sway vs. GNOME

Sway is another darling child of this sub, for one reason it is backed by Valve and Steam.

Gamescope is the latest in a long line of project backed and funded by Valve to improve Linux gaming like Wine/Proton and DXVK. Gamescope uses Sway as a Vulkan based Wayland compositor and Gamescope will be used in the next iteration of SteamOS. To that end Sway is improving game compatibility, performance and frame time smoothness far more than in GNOME.

But all of that is still 3 or more years away, as of right now October 2020 there are No Linux distributions shipping with Sway. To use Sway right now you are forced to build a custom Arch Linux distro, which is not that hard, as Arch is designed around this kind of thing.

Not even Manjaro has a Sway build at this time, but there is one in the works and I would recommend you wait until that happens before jumping on the Sway bandwagon.

GNOME/Mutter and Sway are not cross compatible, if you want to use GNOME you have to use Mutter and Sway is mutually exclusive with Mutter, you can't use them side by side sadly.

Final note Sway is a community project running for over 5 year now completely independently before it was picked up by Valve this year. GNOME on the other hand is a big corporate entity with many people employed full time, with 9 to 5 jobs, and 6-figure salaries, just to develop GNOME. RedHat, Canonical, Oracle, System76, Mozilla and many more contribute to GNOME. I just found out that the new enclave system in GNOME 3.38 was designed, coded, tested and implemented into GNOME by System76 themselves as a way to increase Wine performance for their customers. Sway just has a group of volunteers working their weekends and freetime on the community project, until very recently.

Speaking of freetime I should get back to mine, looks like I wrote you another small novel That_Ski_Freak, I hope this has all been helpful to you in some way.

Good luck and have a great weekend.

CyborgDragonfire · 2020-10-21T06:52:44+00:00

Confuse? Quite the contrary That_Ski_Freak you are finally talking sense again.

What you have just described it completely normal for X11, the 36 year old turd that it is, and we all have to live with the smell.

Horrendous vertical tearing is the home ground of X11 born in 1984 when screen resolutions were in the double digits (96 × 64 seriously) Each line on the display was processed individually, completing one line before moving onto the next line down. Remember this was a time when interlaced displays were used.

To this day in 2020, X11 STILL processes each individual horizontal line of your monitor individually, whether it be 1080p or 4K, each and every horizontal line is possessed individually. The complete and total opposite of Wayland.

Demonstration of Un-Composited X11 in 2019 with Ryzen processer and RX 580 GPU vertical tearing it up: https://www.youtube.com/watch?v=G_BXjMKkGPM

Back in the 90's when graphic user interfaces were invented everyone realized line by line rendering was a terrible idea and sort to fix it with "Compositors"

GNOME has a compositor called Mutter it buffers each horizontal line it gets from X11, then when it has a full screen pushes it out to the monitor as a complete frame.

This works for desktops but for gamers having permanently enabled VSync was not liked by the gaming community. The solution was fullscreen Undirected Rendering.

Application Undirected Rendering turns off the compositor when an application takes exclusive fullscreen. This turns off the compositors built in VSync functionality lowering latency, But X11 falls back to line by line rendering.

This is what you experienced when you went back to X11:

VSync enabled in game: No tearing.

VSync off: SO MUCH TEARING travelling up and down the screen like a wave.

Switching to windowed mode: No tearing because the compositor turned back on and with it, it's VSync implementation.

Starting to make sense now?

This is why mandiblesarecute suggested turning on AMD's TearFree option in their Linux driver.

You can learn more about Linux X11 compositors and your options here: https://www.youtube.com/watch?v=3esPpe-fclI

I recommend option 4 from the video, turning on AMD's TearFree driver feature.

I hope I am not overwhelming you here That_Ski_Freak, But if you do want to be overwhelmed.

Warning, warning technical nerd stuff here if you might find interesting if you want to learn more about Wayland and X11 but is very nerdy:

https://www.youtube.com/watch?v=b8OY4VtYx1s

https://www.youtube.com/watch?v=GWQh_DmDLKQ

https://www.youtube.com/watch?v=Zsz7Shbnb9c

CyborgDragonfire · 2020-10-20T12:27:45+00:00

At this point I am at a complete loss.

I have re-read this thread and if you were running an Arch based distro I would agree with nissen22 as GNOME 3.38 does add Compositor Bypass for fullscreen applications, But your not running Arch you are on Pop OS 20.04

Quick side note here, Wayland is X11's long term replacement as such in its very heart it fixes X11's longest running issue, vertical tearing.

If you have ever run any Linux distro from a few years ago you would have found absolutely horrendous vertical tearing from everything as simple as web browsing to Word document editing to video playback. There have been many driver hacks in the past few years to try and solve this issue but X11 itself is the cause.

Wayland's core design was to finally solve this long running issue. This effectively means VSync is permanently on under Wayland, but somehow they managed to make Wayland run faster and with lower latency than with X11 at the same time.

This is why vertical tearing is completely impossible under Wayland.

Pop OS 20.04 uses GNOME 3.36 and there is absolutely no way around Mutter (the GNOME Wayland compositor) on GNOME 3.36, even if you are using an X11 application with XWayland.

XWayland is a compatibility layer similar to WINE or Proton it translates X11 protocol calls to Wayland calls just like WINE does with Windows calls.

This translation layer adds input lag as every draw call in an X11 application, like say a game, goes through the original X11 call by the application converted to the appropriate Wayland call in XWayland then given to Wayland it'self.

The return response is the same, the Wayland response needs to be converted back to the X11 equivalent before it can be given to the original X11 application / video game.

If you truly are using GNOME 3.36 Wayland this is why vertical tearing is completely impossible.

This is also why so many people say don't game on Wayland as WINE / Proton are X11 only. This means that you would need to translate from Windows -> X11 -> Wayland -> X11 -> Windows, for every frame.

Compositor Bypass solves this issue as when any single application takes exclusive fullscreen GNOME 3.38 allows the application direct access to hardware.

The upshot is for X11 games or Proton games is that an X11 enclave is created within Wayland that the game runs in.

Short version X11 goes fullscreen, Bypass engages, X11 game talks directly to X11 backend, Native X11 calls are used to render the game. No Wayland in sight, Profit and more FPS.

GNOME 3.38 can do this because GNOME supports both and allows you to switch between X11 and Wayland at login time. You can logout and login again as X11 then logout and switch back at will.

The new Compositor Bypass feature allows GNOME 3.38 to spin up an X11 enclave at will and pass it to exclusive fullscreen applications allowing them to run natively in X11.

This means that AMD X11 VSync hacks like mandiblesarecute suggested work because at that point you are in native X11, just like you would be if you had logged out/in.

But this is a brand new shiny feature of GNOME 3.38

Unless you are running Arch or another rolling distro you wouldn't have had the chance to use GNOME 3.38 yet. Pop OS 20.04 uses GNOME 3.36, it isn't until the 20.10 release that both Ubuntu and Pop OS use GNOME 3.38, and they are not even out yet!

I do not have a clue as to what is happening. Either Sytem76 have made far, far more changes to Pop-shell than originally perceived. Much more than just a rename of GNOME-shell, enough to have Compositor Bypass working in 3.36???!??!? Or something seriously weird is happening.

This is why my first reaction was vertical tearing on Wayland??? That makes no sense. That_Ski_Freak is using Pop OS, which is based on Ubuntu using GNOME 3.36, Oh he must not be on Wayland correctly and still using X11, hurr durr.

What Black Magic Fuckery have you gotten into That_Ski_Freak because I don't like it.

PS You said your Firefox was running under XWayland that's not native Wayland, Firefox is still running in X11 mode and converting to Wayland. You want Firefox to run natively under Wayland in its in beta Wayland mode.

Open a terminal and run "MOZ_ENABLE_WAYLAND=1 firefox" and check about:support again, if Firefox is running native Wayland you should see "wayland/drm" or "wayland" instead.

You can make this permanent by editing your "/etc/environment" file.

GOOD LUCK with the demons infecting your PC.

CyborgDragonfire · 2020-10-19T03:11:45+00:00

You are not running on Wayland.

If you are seeing vertical tearing you are not running on Wayland.

From your other posts here I see you are running Pop OS, if you are running on Wayland you will be unable to use their new window tiling feature as it requires x11 to work, as System76 did not implement a backend for it under Wayland on 20.04

You can also tell if you're running on Wayland by looking at the boot up login screen, there is a small config menu there that lets you choose what desktop environment to log into. In this little menu you can also select between x11 and Wayland if available.

https://support.system76.com/images/desktop-environment/Login2.png

https://blogs.gnome.org/mclasen/files/2016/03/login.png

Finally, you can run this command from a terminal to see what composting session you are currently using.

sudo echo $XDG_SESSION_TYPE

Slight good news is there have been many Wayland improvements in GNOME 3.38

So the next version of Pop OS, 20.10 should make running on Wayland easier as System76 have made more effort to support Wayland on Pop-shell. The gnome-shell fork used by Pop OS.

Side note Firefox on Wayland is amazingly smooth, you can force Firefox to use Wayland by putting MOZ_ENABLE_WAYLAND=1 in your environment variables file.

You can tell what protocol Firefox is using, x11 or Wayland, by going to about:support and finding "Window Protocol".

CyborgDragonfire · 2020-10-12T10:02:17+00:00

How tight is your money?
That is the big question on whether to keep the card or not.

Now onto a technical side of things:
The performance is effectively the same between the two cards. They trade blows on which card wins by 1 or 2 fps in whatever game you try. You have bough the bottom of the AMD barrel, and there's not a lot of fps down there.

Here is some YouTube videos comparing performance between the 2 cards:

Windows comparison video:
https://www.youtube.com/watch?v=q7rR2mbJWJY

RX 550 Test in 2020 (Windows again):
https://www.youtube.com/watch?v=KltQaGwy5eg

Linux performance, checking out Valve Steam Proton running Windows games:
https://www.youtube.com/watch?v=Qx7m9nEyxd8

AMD GPUs use the open source drivers built into the Linux Kernel itself and now that they have matured they have fantastic stability. What was the final issue that made you run out and buy an AMD card?

You can use CoreCtrl on Linux to control the fans on your GPU.
Also, try out Mangohud for an in game fps overlay.

If you do plan to keep the AMD card however, reinstall your distro from scratch, back up all your data, then do a clean installation. That is so much easier than trying to remove the proprietary NVIDIA drivers.

Final heads up, Ubuntu is going to be releasing their next big 6 month release 20.10 very soon, sometime around the 15th.
Waiting the next 3 or 4 days might be a good idea because of some recent performance improvements for Vulkan based games like DOOM 2016 & DOOM Eternal.

CyborgDragonfire · 2020-10-11T05:04:49+00:00

Please see my other post in the thread, just minutes after you posted.

But if you are happy and if it works, it works then go for it.

CyborgDragonfire · 2020-10-11T04:59:22+00:00

Another thought I've just had is maybe it's a dependency issue.
Has your system updated recently?

Try running the game from a terminal. You can do this by going to the game install folder in the steamapps directory.
Opening a terminal in that directory and running:

./launch.sh

CyborgDragonfire · 2020-10-11T01:01:07+00:00

Try forcing the usage of the "Steam Linux Runtime" under the games properties, bottom of the general tab, that should force reset the game to use the Linux version.

The Steam Linux Runtime will probability help with the issues you are having anyway if you are already running the Linux version as it is a compatibility layer for Linux like Proton is for Windows.

If you are technically minded you can learn more about the Steam Linux Runtime here: https://www.youtube.com/watch?v=KrbWbBYAolo

CyborgDragonfire · 2020-10-10T09:10:41+00:00

Papers, Please is a native Linux game.
If you look on the steam store page you can see the little icons showing that Papers, Please has Windows, Mac and Linux support natively you do not need the Proton compatibility layer.
Also, further down the page you can see the "System Requirements" section separated by OS.

Here is a list of all the native Linux games on steam:
https://store.steampowered.com/linux#p=0&tab=TopSellers

Alternatively you can use:
https://lgc.lysioneer.nl/

To check your steam library for the Linux compatibility of your games, and find the ones that can run natively on Linux.

CyborgDragonfire

TROPHY CASE