![]() Update-alternatives: using /usr/bin/gnome-terminal. Press to keep the current choice, or type selection number: 1 In my case, I want to use the GNOME terminal instead of the one from Regolith desktop. Press to keep the current choice, or type selection number:Īll you have to do is to enter the selection number. There are 2 choices for the alternative x-terminal-emulator (providing /usr/bin/x-terminal-emulator).Ġ /usr/bin/gnome-terminal.wrapper 40 auto modeġ /usr/bin/gnome-terminal.wrapper 40 manual mode :~$ sudo update-alternatives -config x-terminal-emulator The current default terminal is marked with the asterisk. It will show all the terminal emulators present on your system that can be used as default. Ive also tested to get brltty running in xterm or uxterm. To do that, run the following command: sudo update-alternatives -config x-terminal-emulator I still think to use Mate terminal for textbased work would be a nice solution to not have. You can use it to change the default command line text editor, terminal and more. Obviously I haven't sufficiently purged the previous driver installation.On Debian-based distributions, there is a handy command line utility called update-alternatives that allows you to handle the default applications. The other alternative is to purge delete previous nvidia driver installation, as other tutorials say. So simply deleting /etc/modprobe.d/nf solved the problem. The nvidia-340 driver doesn't use bumblebee. This was apparently a leftover from a previous driver nvidia-304, which was using bumblebee. Its log /var/log/gpu-manager.log was saying: Looking for nvidia modules in /lib/modules/4.4.0-72-generic/updates/dkmsĪnd eventually it updated the alternatives to the mesa/ld.so.conf.įrom this point on it was easy to find out that the nvidia-340 module was indeed blacklisted in /etc/modprobe.d/nf Also the display manager when run manually (not as a systemd service) was using the proprietary driver.Īfter some more investigation it turned out that the culprit was the /usr/bin/gpu-manager (run via /lib/systemd/system/rvice). Startx run from commandline started X correctly with the proprietary driver. and manually inserting the DRI modules ( sudo modprobe nvidia_340 nvidia_340_uvm nvidiafb).setting the alternatives back auto (i.e.I was having the same issue with Dell Vostro 1500 (GeForce 8400M GS, the nvidia-340 driver) after updating to the recent Ubuntu 16.04.2. Slave x-terminal-emulator.1.gz: /usr/share/man/man1/xterm.1.gzīut still, when I hit ctrl+ alt+ t, I get MATE Terminal. Slave x-terminal-emulator.1.gz: /usr/share/man/man1/uxterm.1.gz ![]() Slave x-terminal-emulator.1.gz: /usr/share/man/man1/tilix.1.gz Slave x-terminal-emulator.1.gz: /usr/share/man/man1/mate-terminal.1.gz usr/bin/mate-terminal.wrapper - priority 30 Slave x-terminal-emulator.1.gz: /usr/share/man/man1/lxterm.1.gz Slave x-terminal-emulator.1.gz: /usr/share/man/man1/koi8rxterm.1.gz Slave x-terminal-emulator.1.gz is /usr/share/man/man1/x-terminal-emulator.1.gz Link x-terminal-emulator is /usr/bin/x-terminal-emulator Link currently points to /usr/bin/tilix.wrapper Link best version is /usr/bin/tilix.wrapper ![]() Press to keep the current choice, or type selection sudo update-alternatives -display x-terminal-emulator * 4 /usr/bin/tilix.wrapper 30 manual mode ![]() There are 6 choices for the alternative x-terminal-emulator (providing /usr/bin/x-terminal-emulator).ģ /usr/bin/mate-terminal.wrapper 30 manual mode Have set it as per update-alternatives: sudo update-alternatives -config x-terminal-emulator Running Ubuntu Mate 18.04.1, pretty vanilla install.Īm trying to make Tilix my default terminal emulator. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |