![]() ![]() Thread overview: 7+ messages (download: mbox. Fri Jan 24 14:25:51 2003 my alacritty config file for win10 wsl2. Note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace`Įnd of thread, other threads: Open System Settings - Shortcuts - Add Application, type Alacritty, select it. `thread 'main' panicked at 'Failed to initialize any backend! Wayland status: XdgRuntimeDirNotSet X11 status: XOpenDisplayFailed', /rustc/5c1f21c3b82297671ad3ae1e8c942d2ca92e84f2/src/libstd/macros.rs:13:23 3:28 ` ahesford 3:28 ` ahesford 5 siblings, 0 replies 7+ messages in threadĬlosed issue by unifxfoe on void-packages repository If you need help with your particular setup, I recommend you consult the `r/voidlinux` subreddit or the `#voidlinux` IRC channel on Freenode. This does not appear to be an issue with Void packages. New comment by ahesford on void-packages repository You are better off googling this stuff, it isn't Void specific. No neither are configured could you outline the steps in which I could do so?ĥ siblings, 0 replies 7+ messages in thread New comment by unifxfoe on void-packages repository ` (2 subsequent siblings) 5 siblings, 0 replies 7+ messages in thread The Windows directories in the listing are highlighted with a green background, and when the path overflows one line, the green is extended to the end of the 2nd line. When I open a terminal window and run ls -l, this is what I see. You probably need to use X over ssh or VNC. Ive just installed the Win10 2004 update along with WSL2. Is wayland or X configured in WSL2? AFAIK it doesn't have the graphical stuff by default, which alacritty requires. ` (3 subsequent siblings) 5 siblings, 0 replies 7+ messages in thread 13:19 Not properly working on WSL 2 unifxfoe Is wayland or X configured in WSL2? AFAIK it doesn't configure the graphical stuff by default, which alacritty requires. New comment by ericonr on void-packages repository ` (4 subsequent siblings) 5 siblings, 0 replies 7+ messages in thread 13:19 Not properly working on WSL 2 14:38 ` ericonr I am using WSL 2 and then followed the procedure on the website to build alacritty but to no avail. `thread 'main' panicked at 'Failed to initialize any backend! Wayland status: XdgRuntimeDirNotSet X11 status: LibraryOpenError(OpenError )', /rustc/5c1f21c3b82297671ad3ae1e8c942d2ca92e84f2/src/libstd/macros.rs:13:23` New issue by unifxfoe on void-packages repositoryĪfter building alacritty and running the binary I expected it to open ![]() ` (5 more replies) 0 siblings, 6 replies 7+ messages in thread Now I can't really use chromium though, since I can't install it without snap anymore.ĮDIT: After several hours of trying to fix it I came across several other issues from about 8-10 months ago, with the most popular solution being this, which seems to make some changed to PIDs to make it work, but it just seems so hacky, and it's not a permanent solution, as a restart will remove it.Not properly working on WSL 2 Github messages for voidlinux help / color / mirror / Atom feed * Not properly working on WSL 2 13:19 unifxfoe In my development flow, I like to use the chromium-browser on WSL2 with the X410 server in order to test my web apps in both Windows and Linux browsers, since they can reveal some bugs, like say, when uploading csv files files from a Windows browser, React can't really tell since Windows changes the MIME Type of the file, whereas Linux and Mac keep it the same and so it's easy to handle. Is there any plan to get this working in the future, or is it something that is in progress? Running the command sudo service snapd start simply responds with: So if I run the command snap find node for example, it gives me the following error message:Įrror: cannot communicate with server: Post dial unix /run/snapd.socket: connect: no such file or directory If I understand it correctly, the snapd service should be running in the background for it to work, which snapd already comes preinstalled, however snapd can't start due to WSL2 not having systemd. The issue is that snap doesn't currently seem to work on wsl2 due to it's reliance on systemd. So it's obvious snap is becoming the 'default' of the distro. In fact it seems like Ubuntu 20.04 LTS replaced the ubuntu software with snapcraft entirely. ![]() The main issue I've noticed has to do with a lot of packages moving to snap rather than being maintained on apt, which is how I imagine most people here install their packages. I just reinstalled ubuntu on WSL2 from scratch in order to upgrade to 20.04 with a clean slate. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |