Fedora 21 comes with the ugly Gnome 3, and I installed XFCE and MATE, but I don't know, how to set either of them as a default X window manager. After I logout from Gnome 3, I don't see any selection from installed window managers.
As I interpret your question, you want to install switchdesk
$ yum install switchdesk switchdesk-gui
and run that. You can also try changing settings in /etc/sysconfig/desktop as described here.
If you want to simply try out a different desktop environment at login time, try installing lightdm or kdm (from the fine folks who bring us KDE) and pick one before you log in.
EDIT The advice above maybe outdated.
GDM does not seem to allow you to choose your desktop environment the way KDM and lightdm (and others probably) do. Using my favourite DM, lightdm, as an example (use sudo or switch to root):
$ sudo yum install lightdm
...
$ sudo systemctl reboot
It is possible to do this without rebooting
$ sudo systemctl stop gdm # this will abruptly halt your session and take you to a text console
Log in as root and then type
$ systemctl start lightdm
When I change DM, I like to reboot to make sure my changes persist. If (like mine did) your machine does not boot to a graphical screen, then log in as root and type:
$ systemctl start lightdm
Both KDM and lightdm allow you to select a DE from a pulldown menu.
If you want to revert back to Gnome's display manager:
$ sudo systemctl enable gdm
$ sudo systemctl disable lightdm
GDM does support choosing at login time, but it is sort of hidden.
When I type my login, press Return and before I enter my password a small gear appears. It is a pull-down to choose the desktop environment.
Unfortunately, it is not sticky. I must do it every time. If I get my password wrong the first time, it resets to GDM.
Related
Issue: When I go to share my screen/tab/window on google meet, it comes up very dark.
very dark screenshot of shared screen.
Any ideas how to fix this?
Actions taken: all of the following with multiple logins/out/restarts but to no avail
You might need to update GDM3 custom configuration file
/etc/gdm3/custom.conf
Uncommenting this will force the login screen to use Xorg. #WaylandEnable=false
$ echo $XDG_SESSION_TYPE x11
Install xcompmgr using your Linux distro's package manager. sudo apt install xcompmgr After installing, open the terminal and run this command: xcompmgr -c -l0 -t0 -r0 -o.00 Open compton.conf gedit ~/.config/compton.conf Edit the following line: shadow-exclude = [ "name = 'cpt_frame_window' " ];
added google-chrome-stable --enable-features=UseOzonePlatform --ozone-platform=wayland & to ~/.local/share/applications/google-chrome.desktop
set chrome://flags/#enable-webrtc-pipewire-capturer
sudo mkdir -p /etc/pipewire/media-session.d/ sudo cp /usr/share/pipewire/media-session.d/media-session.conf /etc/pipewire/media-session.d/ sudo sed -i 's/#metadata/metadata/g' /etc/pipewire/media-session.d/media-session.conf
Yours at a complete loss after many hours of digging around :)
OS: Ubuntu: 22.04.1 - clean minimal install
Browsers used: latest Firefox and Chrome
Does anyone have any idea why the loading screen suddenly changed from this:
to this:
Also got some new backgrounds with the Debian logo like this one:
I would very much like to know what caused this and if it could have changed other system settings ( I noticed that the keyring doesn't ask me for a password anymore until I run an app on the computer and also noticed an overall slowness in running apps ). I want to point out that I didn't update nor upgraded the apt repos, I did however removed the ubuntu dock gnome shell extension and added plank, though this happened a few hours before and I rebooted twice in the meantime and the loading screen didn't change.
The second image is from Ubuntu Budgie.
How to Completely Uninstall / Remove Budgie Desktop:
To uninstall the desktop environment, open terminal and run command:
sudo apt remove budgie-desktop-environment budgie-desktop && sudo apt autoremove
And the PPA can be removed by going to System Settings -> Software & Updates -> Other Software tab.
To restore the default login screen (Unity Greeter), run command to remove GTK greeter:
sudo apt remove lightdm-gtk-greeter && sudo apt autoremove
To restore the default start-up splash logo, run command:
sudo update-alternatives --config default.plymouth
Type the number that indicates Ubuntu logo and hit enter.
Set Plymouth theme
And apply the plymouth changes via command:
sudo update-initramfs -u
Taken from: http://tipsonubuntu.com/2016/11/09/install-budgie-desktop-ubuntu-16-04-16-10/
I am trying to configure the networking options for my lxd container but when I try the following command:
lxc network create testbr0
I get the following result:
root#Server02:/var/lib# lxc network create testbr0
Usage: lxc [options]
Checking the list of available commands, I dont see network as an option
Here are the available commands I see:
config, copy, delete, exec, file, finger, image, info, init, launch, list, monitor, move, pause, profile, publish, remote, restart, restore, snapshot, start, stop, version
I'm using Ubuntu 14.04
Any insights?
Thanks
I assume you are using lxd Version 2.0.11. There is no network command in this version.
If you want to use the network command you have to install lxd feature releases (LXD 2.x).
On Ubuntu 14.04 there is no ppa containing the lxd feature releases, so you have to install snap and use the snap package:
sudo apt update
# check if snap is installed, install it if not
if ! type snapctl >/dev/null; then sudo apt install -y snapd; fi
# install lxd
sudo snap install lxd
# wait for lxd startup
while ! echo -e "GET / HTTP/1.0\r\n" | sudo nc -U /var/snap/lxd/common/lxd/unix.socket > /dev/null; do sleep 1; done
# migrate from ppa to snap lxd
sudo /snap/bin/lxd.migrate
# 14.04 does not add the user to lxd group so we do it explicitly
sudo adduser $(id -un) lxd
I'm starting to go nuts over this.
I setup MySQL/Apache/PHP using the tutorial by Coolest Guides On The Planet.
I'm guessing something went wrong as its not working as expected so I want to uninstall and try again.
The trouble is that I can't stop MySQL either by system preferences or command line. I keep trying suggestions on the net but so far unsuccessful.
Can anyone help?
Finally got around the autostart - Thanks to all who contributed and allowed me to see the way.
To stop the auto start I used:
sudo launchctl unload -w /Library/LaunchDaemons/com.mysql.mysql.plist
And to kill the service I used:
sudo pkill mysqld
This is what worked for me. It was listed under a different plist name:
sudo launchctl unload -w com.oracle.oss.mysql.mysqld.plist
For Mac Users
kill -9 {pid} kept restarting the process. This was because I had MySQL Server running. On OSX I had to:
1- System Preferences.
2- Search for mysql.
3- Press the Stop MySQL Server button.
got it from a github issue, and it solved my problem
https://github.com/docker/compose/issues/4950#issuecomment-407145733
brew services stop mysql#5.6 worked for me, when all else failed.
I also got the same problem, unable to stop MySql Sever through system preferences on macOS High Sierra.
I did brew uninstall mysql on my terminal window.
now I am able stop stop MySql Sever through system preferences.
Since mysql was installed on my mac 2 ways binary as well as home brew.
in terminal
kill `pgrep mysqld`
this kills the mysqld process.
If you used brew then you can find out which version you are using by:
launchctl list|grep mysql
this will print something like
92555 0 homebrew.mxcl.mysql#5.7
In my case I'm using mysql#5.7
You can stop using:
brew services stop mysql#5.7
Try with issuing the following command in command line:
ps -xo pid,ppid,stat,command | grep mysqld
It will show you your processes, with their parent ID in the second column. Look for the mysqld and it's parent process. After locating it, issue a:
sudo kill pid
where pid is mysqld's parent process ID.
EDIT
If you want to stop the process from launching again, try:
sudo launchctl unload /System/Library/LaunchDaemons/mysqld.plist
I've installed mysql via homebrew, but stop mysql by using mysql stop command, mysql restart right now.
try to execute command as follow if your mysql was installed via homebrew
brew services stop $(brew list | grep mysql)
I'm running (from Windows 8.1) a Vagrant VM for CoreOS (yungsang/coreos).
I installed kubernetes according to the guide I found here and created the json for the pod using my images.
When I execute sudo ./kubecfg list /pods I get the following error:
F0909 06:03:04.626251 01933 kubecfg.go:182] Got request error: Get http://localhost:8080/api/v1beta1/pods?labels=: dial tcp 127.0.0.1:8080: connection refused
Same goes for sudo ./kubecfg -h http://127.0.0.1:8080 -c /vagrant/app.json create /pods
EDIT: Update
Instead of running the commands myself I integrated into the vagrant file (as such) .
This makes kubernetes work fine. HOWEVER after some time my vagrant ssh connection gets closed off. I reconnect and any kubernetes commands I specify result in the same error as above.
EDIT 2: Update
I managed to get it to run again, however I am unsure if it will run smoothly
I had to re-execute the following commands.
sudo systemctl start etcd
sudo systemctl start download-kubernetes
sudo systemctl start apiserver
sudo systemctl start controller-manager
sudo systemctl start kubelet
sudo systemctl start proxy
I believe it is in fact the apiserver that needs restarting
What is the source of this "timeout"? (Where are any logs I can find for this matter)
Kubernetes development is moving insanely fast right now so this could be out of date by tomorrow. With that in mind, the kubernetes folks recommend following one of their official installation guides. The best advice would be to start over fresh with one of the new installation guides but there are a few tips that I have learned doing this myself.
The first thing to note is that Kubecfg is being deprecated in favor of kubectl. So for future reference if you want to get info about a pod you would run something like:
./kubectl get pods.
With kubectl you will also need to set an env variable so kubectl know how to talk to the apiserver:
KUBERNETES_MASTER=http://IPADDRESS:8080.
The easiest way to debug exactly what is going on if you are using CoreOS is to tail the logs for the service you are interested in. So if you have a kube-apiserver unit you can look at what's goin on by running:
journalctl -f -u kube-apiserver
from the node that is running the apiserver. If that service isn't running, which may be the case, you can start it with:
systemctl start kube-apiserver
On CoreOS you should look at the logs using journalctl.
For example, if you wish to see etcd logs, which Kubernetes relies on for storing the state of it's minions, run journalctl _COMM=etcd, and similarly journalctl _COMM=apiserver will show you the logs from the apiserver, one of key components in Kubernetes.
You also get last few log entries if you run systemctl status apiserver.
Based on errordevelopers advice, my recent installation ran against a similar problem.
Using systemctl status apiserver and sudo systemctl start apiserver I managed to get the environment up and running again.