[-] DeeBeeDouble@lemmy.ml 2 points 6 days ago

I don't think it's OSM but I use Here we go. I don't particularly like it but it has public transport support and isn't Google Maps.

[-] DeeBeeDouble@lemmy.ml 5 points 6 days ago

I like the blur... The rest not so much.

[-] DeeBeeDouble@lemmy.ml 29 points 6 days ago

How can you tell it's plasma? Or is it supposed to be a joke?

[-] DeeBeeDouble@lemmy.ml 17 points 6 days ago

If only it had support for public transport. In theory it would be my favorite OSM app but I can't really use it without support for that :(

[-] DeeBeeDouble@lemmy.ml 17 points 1 week ago

I thought that you would get your grandparents by just going into a train station and picking some random (preferably older person) to be your grandparent.

I was convinced that my parents had done that for me, and that's why I had grandparents.

[-] DeeBeeDouble@lemmy.ml 5 points 2 months ago

And I've just gotten used to Dvorak...

[-] DeeBeeDouble@lemmy.ml 22 points 7 months ago

Any news on wine on Wayland? I haven't heard anything in a while; is it still being worked on?

[-] DeeBeeDouble@lemmy.ml 15 points 8 months ago* (last edited 8 months ago)

I can't see the wizard and the horse anymore lol

[-] DeeBeeDouble@lemmy.ml 9 points 1 year ago

I use the Firefox flatpak on multiple different desktops and distros and I've never seen this issue. All on wayland (no difference on x11 either). Weird.

[-] DeeBeeDouble@lemmy.ml 5 points 1 year ago* (last edited 1 year ago)

Did you also delete the steam user data when reinstalling it? Regardless, I found a Github issue that looks very similar to yours. Apparently this was caused by a beta update? But this was about 4 months ago? Weird.

Anyway, the suggested fix was to first reset steam with flatpak run com.valvesoftware.Steam --reset And then opt out of any potential beta: com.valvesoftware.Steam -clearbeta

Not sure if this really is the same issue, but it's definitely worth a try.

Edit: Seems like on some systems, removing the package xdg-desktop-portal-gnome also fixed it. Don't know if it also applies to the flatpak, but just try it. Just remember to install the package again if it doesn't fix it. It may be needed for some other things.

[-] DeeBeeDouble@lemmy.ml 16 points 1 year ago

They are no longer on reddit. If I hadn't reposted them here, they would have been lost forever.

[-] DeeBeeDouble@lemmy.ml 14 points 1 year ago

I know, right? It's funny how all of my posts here so far are just old ones from Reddit...

460
submitted 1 year ago by DeeBeeDouble@lemmy.ml to c/linux@lemmy.ml

All credits go to former Reddit user u/Err404UNameNotFound

He decided to delete his account and gave me permission to repost his work here.

4
submitted 2 years ago* (last edited 2 years ago) by DeeBeeDouble@lemmy.ml to c/linux_gaming@lemmy.ml

Note: This was originally posted on Reddit. However, I have now decided to move the guide to lemmy and I will most likely delete the one on Reddit soon.

There are multiple options to achieve Wayland screen sharing with discord. I will cover two here.

OPTION 1 (Recommended):

There is a web-based discord client for Linux called "Webcord" that supports Wayland screen sharing. You just have to install it, open it, sign in, and you're done.

You can install it by downloading your preferred package from here or by using the flatpak version avaliable on flathub.

If you dont have flatpak set up - here is another quick guide.

That's it! You can now start screen sharing on Wayland!

In case you are interested in streaming your desktop audio as well, there is another Discord client called discord-screenaudio to do just that. It is also available on flathub.

OPTION 2:

What you'll need:

Step1:

Open WebApps and click on the little + icon in the bottom. Fill in the name (Discord) and the web Address (discord.com/app). The icon should apply automatically. As a browser, choose your Chromium-based browser. Then activate the switch "Isolated Profile" and click Ok.

Step2:

You now should be able to find Discord in your application-launcher of your choice. If you see discord twice, that means that you have now both the "real" Discord app and the new WebApp. Then try to launch the WebApp Discord. You now can sign in and use discord just as normal. However, there is still no Wayland support. We will activate it in step 3.

Step3: (unnecessary if you use Firefox)

While in the WebApp Discord, press Ctrl+T. A new window should appear. Then type chrome://flags in the address bar and press enter. Now search for "WebRTC PipeWire support" and change it from default to true. Now click "Relaunch" in the bottom of the window. If you have done everything right, you should now have Wayland support :)

I hope I could help you in some form, and have a nice day!

Optional: (And for more advanced users) Running the Discord WebApp without the use of Xwayland

Since Chrome version 97:

While in the Discord WebApp, press Ctrl+T. Type chrome://flags in the address bar and hit enter. Search for "Preferred Ozone platform". Change it from "Default" to "Auto". Then relaunch Discord. That's it.

Chrome Versions below 97:

Note: This is ONLY tested with arch/Manjaro and Brave. It could work on other systems and browsers too, but this is not guaranteed. So you basically just have to enable chromium Wayland flag. You can do this by creating a config file at $HOME/.config/brave-flags.conf. Do that by running nano $HOME/.config/brave-flags.conf (If you are running another browser than Brave, I guess you could replace brave with the name of the other browser, but I didn't test this). Now insert the flag --enable-features=UseOzonePlatform --ozone-platform=wayland save it by pressing Ctrl+O and exit with Ctrl+X. Now launch Discord again and see if it runs natively on Wayland. You can do this by installing and running xeyes (when installed, simply run xeyes in your terminal). When you move the mouse over a window and the eyes are moving, it uses Xwayland or X11. If not, you successfully activated Wayland.

view more: next ›

DeeBeeDouble

joined 2 years ago