{{Header}} {{Title|title= Platform-specific Desktop Tips }} {{#seo: |description={{project_name_long}} Platform-specific Desktop Tips and Tricks, RAM Adjusted Desktop Starter, Virtual Console, Full-Screen }} {{intro| {{project_name_short}} Platform-specific Desktop Tips and Tricks, RAM Adjusted Desktop Starter, Virtual Console, Full-Screen }} = All Platforms = == Disable Terminal Emulator Banner == The following greeting banner appears when a terminal shell bash prompt is opened.
Welcome to {{project_name_short}}! https://www.{{project_clearnet}} {{project_name_short}} Copyright (C) 2012 - 2024 ENCRYPTED SUPPORT LP {{project_name_short}} is Freedom Software, and you are welcome to redistribute it under certain conditions; type "{{project_name_short_lowercase}}-license" for details. {{project_name_short}} is a compilation of software packages, each under its own copyright and license. The exact license terms for each program are described in the individual files in /usr/share/doc/*/copyright. {{project_name_short}} GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent permitted by applicable law; for details type "{{project_name_short_lowercase}}-disclaimer" . {{project_name_short}} is a derivative of Debian GNU/Linux and based on Tor. {{project_name_short}} is produced independently from the Tor (r) anonymity software and carries no guarantee from The Tor Project about quality, suitability or anything else. {{project_name_short}} is experimental software by means of concept and design. Do not rely on it for strong anonymity. Type: "{{project_name_short_lowercase}}" for help. uwt INFO: Stream isolation for some applications enabled. uwt / torsocks will be automatically prepended to some commands. What is that? See: uwt INFO: https://www.whonix.org/wiki/Stream_Isolation/Easy
To disable the banner, follow these steps. {{Box|text= '''1.''' {{Open_a__product_ws_terminal}} '''2.''' Run the following command. {{CodeSelect|code= cp /etc/skel/.bashrc.{{project_name_short_lowercase}}-orig ~/.bashrc }} '''3.''' Done. The process is now complete. }} See also: [[#Disable Virtual Console Banner|Disable Virtual Console Banner]]. == Shut Down {{project_name_short}} == To shut down {{project_name_short}}, open a terminal and run. {{CodeSelect|code= sudo poweroff }} Alternatively, use the menu option: * [[Non-Qubes-Kicksecure|{{non_q_project_name_short}}]]: Start Menu → Log Out → Shut Down * [[Qubes|{{q_project_name_long}}]]: Blue Q button → Qubes Tools → Qubes Manager → {{project_name_gateway_vm}} → Shutdown {{Non-qubes-project}} == Virtual Consoles == === Using {{project_name_short}} as a Host Operating System === [https://en.wikipedia.org/wiki/Virtual_console Virtual consoles] is a feature inherited from Debian GNU/Linux which is unfamiliar to many users. The following keyboard shortcuts activate the Debian (not {{project_name_short}}) feature: * Text console: Press Alt + Crtl + F1 ** Additional text consoles: Press Alt + Crtl + F2 or F3 and so on. * Graphical console: Press Alt + Crtl + F7 '''Figure:''' ''virtual console login'' [[File:virtual_console.png|600px]] === Virtual Machines === '''Table:''' ''Virtual Console Activation'' {| class="wikitable" |- ! scope="col"| '''Platform''' ! scope="col"| '''Steps''' |- ! scope="row"| KVM | The desired virtual console key shortcut can be selected under the Send Key option in a VM's graphical window. |- ! scope="row"| Qubes dom0 | Qubes dom0 inherited the same feature (Alt + Crtl + F1...). |- ! scope="row"| Qubes VMs | In order to access VMs in dom0, run: This is not a real virtual console, but using login. sudo xl console vm-name. Replace "vm-name" with the name of the actual VM, for example. {{CodeSelect|code= sudo xl console {{project_name_gateway_vm}} }} See also [https://github.com/QubesOS/qubes-issues/issues/5492 add Qubes host key to allow switching virtual console (ctrl + alt + F1) or SysRq for HVM]. |- ! scope="row"| VirtualBox | The VirtualBox default is Right Ctrl + F2. Inside VirtualBox, the Alt + Ctrl keys are already registered by the host operating system. Host key can be changed using VirtualBox → Global Settings → Input → Host Key. * Text console: Press Right Ctrl + F2 (F1, F2, F3, F4...) for one or more text consoles. * Graphical console: Press Host Key + F7 for a graphical console inside VirtualBox. |} Due to technical limitations, an easier to understand presentation like {{project_name_short}} username login: or something similar cannot be shown. The login program unfortunately does not provide this option. # Enter your username (this is most likely user) and press . # Enter your password and press . {{Default_Passwords}} === Disable Virtual Console Banner === This process is similar to [[#Disable Terminal Emulator Banner|Disable Terminal Emulator Banner]]. '''1.''' Open a [[#Virtual Consoles|virtual console]]. '''2.''' Run the following command to restore the original bashrc (untested). Please leave feedback if this step works correctly. {{CodeSelect|code= cp /etc/skel/.bashrc.whonix-orig ~/.bashrc }} '''A)''' Run the following command. {{CodeSelect|code= sudo unlink /etc/motd }} '''3.''' Done The procedure is complete. = {{non_q_project_name_short}} = == Disable Autologin == [[File:Gui_login.png|thumb|graphical login screen (by login manager LightDM)]] Autologin is enabled by default in the login manager by {{project_name_short}}. * '''Host operating system:''' ** '''Simple login screen:''' Disabling autologin can be useful if the user wants to enable a login screen. ** '''No full disk encryption:''' Note, the login screen is not providing [[Full_Disk_Encryption|Full Disk Encryption (FDE)]]. The purpose of the login screen is elaborated in chapter [[Protection_Against_Physical_Attacks#Login_Screen|Login Screen]]. * '''VMs:''' It is not very useful to disable autologin to enable a login screen inside VMs. It's much more secure to have a login screen on the host operating system. This requires configuration of LightDM in {{project_name_short}}. '''1.''' Disable LightDM autologin. This is done by deleting the configuration files which enable autologin. {{CodeSelect|code= sudo rm /etc/lightdm/lightdm.conf.d/30_autologin.conf }} {{CodeSelect|code= sudo rm /etc/lightdm/lightdm.conf.d/40_autologin.conf }} '''2.''' Linux user account password. The user will need to [[Post_Install_Advice#Change_Passwords|set a Linux user account password]] if one has not already been set. '''3.''' Reboot. '''4.''' Done. Autologin should be disabled after reboot and the user should see a login prompt after reboot. '''Troubleshooting:''' See footnote for troubleshooting. GDM configuration. GDM is a login manager different from LightDM. Only very old versions of {{project_name_short}} come with GDM installed by default. '''1.''' Open the GDM configuration file. Note, if the file is empty that means it doesn't exist. In that case, skip this. {{Open with root rights|filename= /etc/gdm3/daemon.conf.dist }} '''2.''' Search for the following. 
AutomaticLoginEnable=true
AutomaticLogin=user
'''3.''' Modify. Out-comment, add a hash symbol ("#") in front of the two lines. Or replace the content, copy/paste the following which does the same. {{CodeSelect|code= #AutomaticLoginEnable=true #AutomaticLogin=user }} '''4.''' Save. See also: [[Login]] == Minimal RAM Required == {{project_name_short}} is based on Debian stable releases thus it will use similar [https://www.debian.org/releases/stable/amd64/ch02s05.en.html Memory and Disk Space Requirements] for Debian. == RAM Adjusted Desktop Starter == {{RAM_Adjusted_Desktop_Starter}} For more information, see [[RAM Adjusted Desktop Starter]]. == Disable the Graphical Desktop Environment == This is for advanced users only. To stop the graphical desktop environment. {{CodeSelect|code= sudo systemctl stop gdm3 }} To disable automatic start at boot of the graphical desktop environment. {{CodeSelect|code= sudo systemctl disable gdm3 }} To restart the graphical desktop environment. {{CodeSelect|code= sudo systemctl start gdm3 }} To re-enable automatic start at boot of the graphical desktop environment. {{CodeSelect|code= sudo systemctl enable gdm3 }} To uninstall the graphical desktop environment software packages, not that understanding [[Debian Packages|{{project_name_short}} meta packages]] is prerequisite knowledge. Then package non-qubes-whonix-gateway-xfce / non-qubes-whonix-workstation-xfce can be removed. Or alternatively, download the {{project_name_short}} CLI version or build it from source code. related: Using [[Other Desktop Environments|{{project_name_short}} with Other Desktop Environments such as GNOME, KDE, LXDE, MATE, ...)]] == Use Full-screen Mode == It is recommended to work in full-screen; this feature is also inherited from [[VirtualBox]]. To activate and deactivate full-screen mode, press the VirtualBox Host Key + F. The current Host Key is visible in the bottom right corner of VirtualBox. The VirtualBox default is Right Ctrl + F. Host key can be changed using VirtualBox → Global Settings → Input → Host Key. Full-screen mode leads to the {{project_name_short}} (and Debian) default resolution and color depth of 1920x1080x24. {{Anchor|Whonixcheck / Timesync Writing to tty1}} == Xfce Scaling == A number of displays found in high-end laptops and desktops have High Dots Per Inch (HiDPI), providing a high resolution in a relatively small format. High-resolution mode can cause problems with certain software and the following adjustments may be necessary to improve HiDPI presentation in Xfce. https://wiki.archlinux.org/title/HiDPI#Xfce '''Table:''' ''Xfce Scaling Options'' {| class="wikitable" |- ! scope="col"| '''Configuration''' ! scope="col"| '''Description''' |- ! scope="row"| Fonts | Change the DPI (dots per inch) parameter as follows: * Settings Manager → Appearance → Fonts → DPI → Increase For example, it is reported that a value of 180 or 192 seems to work well on Retina screens, but trial and error may be necessary to get a more precise number for the relevant display. |- ! scope="row"| gtk2 Menus and Buttons | Follow these steps to change the default icon sizes of gtk2 menus, buttons and so on: * Settings Manager → Settings Editor → xsettings → Gtk → IconSizes → in row Value → add the following line. {{CodeSelect|breaklines=true|code= gtk-large-toolbar=96,96:gtk-small-toolbar=64,64:gtk-menu=64,64:gtk-dialog=96,96:gtk-button=64,64:gtk-dnd=64,64 }} Note that the "gtk-dnd" parameter is for the icons during drag'n'drop, while the others are self-evident based on their name. Any value supported by the icon theme can be used. |- ! scope="row"| System Tray Icon Size | Follow these steps to enlarge icons in the system tray: # Right-click on system tray: aim for empty space / top pixels / bottom pixels, so the the icons are not activated themselves. # Properties → Set "Maximum icon size" to 32, 48 or 64. |- ! scope="row"| Task Bar Size | To change the size of the task bar: * Right-click on empty space in task bar → Panel → Panel Preferences → Row Size (Pixels) → move slider |- ! scope="row"| Window Manager Style | Xfwm has two hidpi themes: Default-hdpi and Default-xhdpi. Change the theme as follows: * Settings Manager → Window Manager → Style → Theme → Default-hdpi or Default-xhdpi |- |} {{Anchor|Xfce Settings Reset}} == Default Home Folder Configuration Files Reset == Before following these instructions to wipe the whole Xfce settings folder and restore defaults, it is recommended to backup existing Xfce settings. {{Box|text= '''1.''' Open a [[Desktop#Virtual_Consoles|virtual console]]. '''2.''' Logout from and stop Xfce by halting {{project_name_short}} default login manager gdm3. {{CodeSelect|code= sudo systemct stop gdm3 }} '''3.''' Trash folder ~/.config/xfce4. '''4.''' Delete the first-boot-skel.done file. {{CodeSelect|code= sudo rm /var/cache/anon-base-files/first-boot-skel.done }} '''5.''' Re-add {{project_name_short}} Xfce configuration files. {{CodeSelect|code= sudo /usr/libexec/helper-scripts/first-boot-skel }} '''6.''' Restart the display manager to restart Xfce. {{CodeSelect|code= sudo systemctl restart gdm3 }} '''7.''' Done. The process has been completed. }} = {{q_project_name_short}} = == Avoid VM Full Screen Mode == It is unrecommended to allow [[Qubes|{{q_project_name_short}}]] or other VMs to [https://www.qubes-os.org/doc/how-to-enter-fullscreen-mode/ completely "own" the full screen]. Overriding Qubes' GUI virtualization daemon restrictions means the colored decorations drawn by each VM window will not be visible. In this case, a malicious application might not actually release the full screen (while it appears normal), or the full desktop may be emulated so users are tricked into entering sensitive information inside false "trusted" domains. https://www.qubes-os.org/doc/how-to-enter-fullscreen-mode/ = See Also = * [[Keyboard Layout]] = Footnotes = {{reflist|close=1}} {{Footer}} [[Category:Documentation]]