Centos 8 ships with Wayland as its compositor and I was forced to install centos8 due to some GLIBCXX compatability issue. Everything SEEMS to work ok but there is a curious absence of all xapps and I cant get a remote X11 session going. It seems I am in Wayland hell.
Centos 8 ships with the shiny new Wayland with rumored X11 compatibility, but all I find is articles on rumors of xwayland and a host of badly named products whose names all begin with 'W' for cute.
I cant seem to install any x11, xapps or anything that would force xwayland to install as a dependency. Its amazing how easily a decision is taken to burn thousands of hours on tens of thousands of users globally.
My best google-fu has yielded nothing.
Please help. How can I get x11 (xwayland) up and running so that I can run apps from my Windows desktop as I used to with Centos 7...?
I've already encountered this "problem" and the solution I usually apply is to disable WayLand.
To do this, just edit this file with any editor (I use VI)
/etc/gdm/custom.conf
and change the line
#WaylandEnable=false
into
WaylandEnable=false
Save and close the file and restart gdm service with
systemctl restart gdm.service
Related
Hoping this is the right place to ask this. I'm trying to learn React Native and I'm using Expo as my medium for deployment, but I'm finding that I'm literally getting 20 minutes at a time before my browser fails to connect with the error code ERR_CONNECTION_FAILED. I've tried the following:
netsh winsock reset, then the related ipconfig commands for flushing DNS settings
Clearing browser caches
Updating drivers
I'm at my wits end as the only thing that completely solves it is restarting my laptop, which for obvious reasons isn't feasible every 20 minutes, so I'm hoping somebody can help.
I'm experiencing the same issue with Expo in this environment:
Windows 10, version 1909 (OS build 18363.476)
using WSL (Windows Subsystem for Linux) with Ubuntu 18.04 LTS
These links were useful to learn why this is happening:
https://github.com/expo/expo-cli/issues/99
https://github.com/microsoft/WSL/issues/2913
https://github.com/microsoft/WSL/issues/3951
In essence, this issue seems to be due to a problem with WSL. Per a post in the first link, I tried the alternative to restarting the computer and it worked - it made the ERR_CONNECTION_FAILED problems disappear...for 20 minutes. That alternative is as follows:
WIN+R -> services.msc
Find LxssManager
Right-click -> Restart
This restarts the WSL service which also means that the WSL instance that was running gets terminated. This is less than ideal, but at least a computer restart is avoided. The third link says this WSL problem is fixed in Windows Insider Build 18890.
I am now considering spinning up a VM to run Ubuntu instead of trying to use WSL for Expo projects.
I uninstalled the latest Windows updates, and the problem has not surfaced since.
I've got MAMP Pro 4 installed on my Windows machine.
Everything works correct, but I cannot enable the automatic start when the OS launches.
In fact, the checkbox "Start Groupstart Servers on System Startup" in the Ports page is disabled and I cannot check it.
So, the question is, how can I enable that option?
Since I haven't find any solution searching on the web, I've decided
to ask here. MAMP is not very diffused on Windows, it would be good to
spread some informations, I like it as I used it on my old Mac (the
only thing that I don't like is the amount of languages installed:
ruby, perl, etc.. Maybe with a custom install one can avoid to install
them, but I missed that this time).
I have installed debian 9.3 on HP DL20 Gen9. When Debian 9.3 start, what happen is that the screen of the system appear like on the picture after the grub goes. any help?
Try booting your computer up in safe mode from Grub. Install updates and restart.
If it happens again you probably need to configure your graphics card for your installation.
Re-install Debian 9, when in the Software selection menu,
don't enable Debian Desktop Environment. If you need a desktop environment, simply enable certain Desktop environments.
In this case, I'm using Cinnamon. Until now there are no problems.
Thanks.
I find a solution. I used "nomodeset on the boot", and the screen appear normaly. I have used another tty2 and i get connected with the shell.
nano /etc/default/grub
i find this:
GRUB_CMDLINE_LINUX_DEFAULT="quiet"
and i have changed it to this:
GRUB_CMDLINE_LINUX_DEFAULT="quiet nomodeset"
I have a dell inspiron 5559 and i used to have a dual boot windows 10 and ubuntu 16.0.4.
After an update of windows 10 i got many problems like my graphic card driver didnt get auto-update and my cpu fan got some problem
After changing my fan windows would enter an automatic repair and before even starting it... it would jump into blue screen and enter a restart loop while my linux would work just fine
I tried installing or repairing windows but before the page for chosing language blue screen apears again and system jumps out of installation
I started a system diagnose and ram memmory test but there wasnt any error.
So i thought maybe its grub menu or linux's problem and i used rm rf root in ubuntu (that was a foolish mistake im really sad about this now) after that still i cant install or repair windows. and when i turn on my pc an error apears
//
Error: file '/boot/grub/i386-pc/normal.mod' not found.
Entering rescue mod...
Grub rescue>
//
I tried different windows dvd's for installation all had same problem. And i tried installing or trying ubuntu or kali live using an usb but various errors show up like bootmgr is missing or....
Can anyone help?
Sorry if my text had some english problems :)))
May be formatting the entire hard drive then install Windows or Ubuntu would work for you.
I installed RHEL 6.4 server under Parallels 7 on my Mac OS 10.8 just now from an iso file I just downloaded from RedHat. The installation seemed to proceed ok, but at the end I'm left with a screen with a gray bar followed by the text "RedHat Enterprise Linux Server 6.4" with no obvious way how to login.
If I shut down the machine I see it running the shutdown scripts. If I boot it I see the boot scripts and they all look ok. But I always end up at that same screen with no way to login.
I can enter characters in the screen, but there is no Linux prompt at all.
Anybody know what to do next? I couldn't glean anything fro the RedHat install manual.
Thanks,
doug
I had the same problem. The issue is the X-win server will not start because Parallels tools breaks the framebuffer with the RHEL 6.4 update. This is especially easy to see because a fresh install works fine until you install Parallels tools.
When you see the "select system to boot" message, hit the key that allows you to edit the boot arguments. Add a "3" to the end to force the startup to runlevel 3 (which is a console login without the GUI).
After logging in, type the command "starts" and you will see that it fails. Once you are able to fix this problem, the normal bootup into the GUI login will also work.
I had to downgrade the video driver subsystem back to 6.3 for it to start working, and you also have to add an exclusion to yum to prevent it from updating and removing the fix. This will be necessary until Parallels releases an updated tools that addresses this issue. There is a procedure I found in the CentOS forums for how to do this, sorry I don't have the link.