developer-center VS sway

If you have any questions or suggestions about the system, please feel free to join the discussion on the Deepin forum: **https://bbs.deepin.org. Meanwhile, if you find any bugs while using the system, please don't hesitate to report them to us by opening an issue at https://github.com/linuxdeepin/developer-center/issues. Thank you for your support!

Sorry, https://github.com/linuxdeepin/developer-center/issues/2755

https://github.com/linuxdeepin/developer-center/issues/2819 usually less extreme, but it's an outcome of how X11 is designed

Welcome to discuss the features you want in the starting stage of this project at https://github.com/linuxdeepin/developer-center/discussions/3236.

Abort the installation. Try again, you may also try to flash the USB stick again. If this won't work, report issue here https://github.com/linuxdeepin/developer-center/issues

Done - https://github.com/linuxdeepin/developer-center/issues/3010

Create issue here and say what you did so far. https://github.com/linuxdeepin/developer-center/issues It look like it may be a mesa bug, but let's ask deepin devs first

I already reported this issue here https://github.com/linuxdeepin/developer-center/issues/2138. It's probably a problem for everyone. I guess It'll be fixed in December in next release https://www.deepin.org/en/developer-community/planning/

Im not sure there is anything you can do. Deepin is currently using ver. 460 driver which is relatively outdated and probably doesn't even introduce support for 3060. I'd look up if that's really the case and if yes let devs know of this issue https://github.com/linuxdeepin/developer-center/issues

This is partially why i use tools like i3 (/ sway). i like the tool; it works extremely well for me; the design has stayed the same for 20 years; there's no profit motive to come along and fuck everything up. it just works. it is boring in the best way possible.

I also have crashes on sway, but there’s a rough workaround now which prevents the issue totally.

I believe there’s a design issue with Firefox and GTK handling input events; some Wayland compositors have workarounds but others do not.

https://github.com/swaywm/sway/issues/7645

https://bugzilla.mozilla.org/show_bug.cgi?id=1743144

Firefox is my preferred browser and I hope we can keep its engine alive in this era of Chrome dominance.

I'm seeing this: https://github.com/swaywm/sway/wiki/Setting-Environmental-Variables but I haven't figured out how to make GDM do it, and I was wondering if there was a super simple "HEY SWAY READ MY .PROFILE" thing I could do.

So I searched around and found the following bug report where this problem and a possible solution was borough up: https://github.com/swaywm/sway/issues/2966 , which was then immediately closed again.

I've been using Sway since late 2019. I like the workflow of a WM. I honestly find it hard to go back to a DE, I like having a minimalistic desktop.

Sway is fast, minimal, and flexible. Their recommended tools/addons are worth a look: https://github.com/swaywm/sway/wiki/Useful-add-ons-for-sway

From that list I use greetd + tuigreet as my login manager, sway-launcher-desktop for FZF-powered app launching, and wob for lightweight brightness and volume display (send '50' to the wob socket and it'll show 50%; it doesn't get simpler).