Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.lang.javascript > #102429

Software Xwin Avs Download !!HOT!!

Show all headers | View raw

It's working otherwise just as intended but for some reason it's spawning two xwin-xdg-menu processes of which the other one is consuming 25% of my CPU. When I kill it, the CPU usage returns to normal and everything is working fine, including the other xwin-xdg-menu process.


It seems I'm not the only one with this problem but for now I haven't found any solution to this. -05/msg00345.html -at-spi-bus-launcher-and-xwin-xdg-menu-high-cpu (I don't have problems with at-spi-bus-launcher though)



software xwin avs download

DOWNLOAD https://t.co/TY8DkHcTXa 






Reason I suspect this worked:

startxwin searches for a /.startxwinrc file to execute when launching. If startxwin does not find a /.startxwinrc file, startxwin will follow the default routine outlined in /etc/X11/xinit/startxwinrc.


The default routine launches /usr/bin/xwin-xdg-menu, somehow causing me to have two xwin-xdg-menu processes, one of them with very high cpu. Creating /.startxwinrc bypasses the default routine, disabling /usr/bin/xwin-xdg-menu from launching altogether.


Whenever I start Cygwin's X server using the "XWin Server" link in my Start menu, or by running startxwin from a Cygwin shell, I automatically get an xterm window appearing, which I neither want nor need.


If no specific client program is given on the command line, startxwin will look for a file in the user's home directory called .startxwinrc to run as a shell script to start up client programs. If no such file exists, startxwin will use the following as a default:


It is possible to run XWin.exe directly from within a Bash login shell, without the surrounding tasks that startxwin and xinit perform. The main advantage of this is that it behaves like we want: the X server starts and remains running. Unfortunately, since there is no .Xauthority file passed during startup, your X server would permit any local process to connect to it, which is insecure.


From now on, the startxwin script will call XWin.exe directly, rather than calling xinit. Obviously this will disable any client rc scripts, but we didn't want those in the first place. It also means that X will continue running without needing a client process to keep it alive (i.e. keep xinit from killing it).


I installed cygwins X Server to be able to X forward on Windows 10 as explained here. Now the installation completed and it finished without problems, but when I try to start the XWin Server as explained on the offical site a window opens shortly but immediately closes again. I tried to use the command C:\cygwin64\bin\run.exe --quote /usr/bin/bash.exe -l -c "cd; exec /usr/bin/startxwin" instead of using the shortcut but the same thing happens. A window opens briefly but no output in the console.Starting a cygwin terminal and running /usr/bin/startxwin returns:






So instead, I just took inspiration from other projects and created my own xwin program to download, decompress, and repackage the MSVCRT and Windows SDK into a form appropriate for cross compilation. This has several advantages over using the official installation methods.


We have two basic options for how we could get the CRT and SDK, either run xwin directly during image building, or run it separately and tarball the files and upload them to something like GCS and just retrieve them as needed in the future. We'll just use it directly while building the image since that's easier.

 f5d0e4f075

Back to comp.lang.javascript | Previous | Next | Find similar | Unroll thread

Thread

Software Xwin Avs Download !!HOT!! Luisa Mova <lmova8864@gmail.com> - 2024-01-24 10:14 -0800

csiph-web