![]() What socat does is connect two arbitrary streams/sockets together. QEMU 2.8.1 monitor - type 'help' for more information You can use the socat utility (available from all good repositories) to connect to the socket to type commands to the QEMU monitor prompt: $ socat -,echo=0,icanon=0 unix-connect:qemu-monitor-socket The options server,nowait tell QEMU to listen for connections, but start the VM without waiting for a connection. You'll see this file created when QEMU starts. Qemu-monitor-socket here is not a keyword, but a host path and filename of your choice to represent the socket on disk. When you start QEMU, add the -monitor parameter as follows: $ qemu-system-i386 -monitor unix:qemu-monitor-socket,server,nowait It works well, although the method is very poorly documented. Tasksel-data tzdata udev unzip update-glx usb.My preferred way to do this is to connect to the QEMU "monitor" via a UNIX socket. Samba-dsdb-modules samba-libs systemd-sysv sysvinit-utils task-english tasksel Qemu-system-gui qemu-system-x86 qemu-utils rsyslog samba-common samba-common-bin Openssl python3-ldb python3-libxml2 python3-samba qemu-system-common qemu-system-data Nvidia-modprobe nvidia-persistenced nvidia-settings nvidia-vulkan-common openssh-client Linux-libc-dev locales logrotate nano ntfs-3g nvidia-egl-common nvidia-legacy-check Libxml2:i386 libxml2-utils libxnvctrl0 linux-compiler-gcc-10-x86 linux-kbuild-5.10 Libxenhypfs1 libxenmisc4.14 libxenstore3.0 libxentoolcore1 libxentoollog1 libxml2 Libxencall1 libxendevicemodel1 libxenevtchn1 libxenforeignmemory1 libxengnttab1 Libtirpc3 libtirpc3:i386 libudev1 libudev1:i386 libwbclient0 libwebkit2gtk-4.0-37 Libswresample3:i386 libswscale5 libtiff5 libtiff5:i386 libtirpc-common libtirpc-dev Libnvidia-encode1 libnvidia-encode1:i386 libnvidia-rtcore libostree-1-1 libpostproc55 Libldap-common libldb2 liblzma5 liblzma5:i386 libntfs-3g883 libnvidia-cbl Libfreetype6:i386 libfribidi0 libfribidi0:i386 libgnutls30 libgnutls30:i386 libgtk-3-0 Libexpat1 libexpat1:i386 libflac++6v5 libflac8 libflac8:i386 libfreetype6 Libcurl3-gnutls:i386 libcurl4 libcurl4:i386 libdpkg-perl libexo-2-0 libexo-common Libc-l10n libc6 libc6:i386 libc6-dev libcups2 libcups2:i386 libcurl3-gnutls Libavresample4:i386 libavutil56 libavutil56:i386 libc-bin libc-dev-bin libc-devtools Libavcodec58:i386 libavdevice58 libavfilter7 libavformat58 libavresample4 Gstreamer1.0-plugins-good:i386 gtk-update-icon-cache gzip libarchive13 libavcodec58 Gpg gpg-agent gpg-wks-client gpg-wks-server gpgconf gpgsm gpgv gstreamer1.0-plugins-good Glx-alternative-mesa glx-alternative-nvidia glx-diversions gnupg gnupg-l10n gnupg-utils ![]() Screenshot_20-15-10.png (32.52 KiB) Viewed 1128 timesĬode: Select all base-files bash bind9-dnsutils bind9-host bind9-libs cifs-utils cups-client cups-commonĬurl dirmngr distro-info-data dpkg dpkg-dev exo-utils ffmpeg firefox-esr gir1.2-gtk-3.0 The wiki doesn't really say what to do when you actually try to print something and if there is anything particular I need to do with the print dialogue box. UPS_Serverīut I still end up at the same system print dialogue box when I try to print with the same issue. To try and resolve this I followed this guidance on the Debian wiki. Nothing is wrong with the CUPS server as I can print from all my other devices. ![]() I have no idea what caused this issue suddenly (maybe a package update perhaps?). Now when I go to the print dialogue box, the printer still appears but when I select it I get the message "Getting printer information" with a cursor spinning wheel and the print button stays disabled. When I go to the system print dialogue box the remote printer appeared without having to do anything and I was able to print. Well it worked until recently and suddenly stopped working unexplicably.īasically I do not want to install CUPS server on my machine just to print to a remote CUPS server. I have a CUPS print server setup on a Raspberry Pi that works with all my devices except my Debian 11 XFCE install.
0 Comments
Leave a Reply. |