Re: [qubes-users] Deleting app VMs in Qubes 4.0 doesn't free up disk space
‐‐‐ Original Message ‐‐‐ On Thursday, October 11, 2018 11:02 PM, 'awokd' via qubes-users wrote: > > On further investigation, I discovered that > > /var/log/xen/xenstored-trace.log in dom0 was 155GB. > > I don't have this log on mine. Did you maybe enable it somewhere? Yes, and then I forgot to disable it when I was done with it. Then the extreme growth of the log coincidentally (!) canceled out the space freed up by deleting qubes, which accounted for the surprising behavior I was seeing. > > But qvm-pool -vi lvm still reports 99% HD usage (468GB used out of 473GB > > size for pool00)! The HD is 500GB, so trimming 80.7GiB should have freed > > 17%. > > OTOH, sudo lvs did report that pool00 data% dropped from 99 to 67, and > > meta% dropped from 55 to 39. So the problem is clearly with Qubes, not LVM. > > Have you rebooted since cleaning up? Maybe qvm-pool just hasn't caught > up yet. I noticed some hours later that qv-pool finally caught up. Don't know what triggered it (but not a reboot). Also don't know why lvs and qvm-pool should ever report different free space values, but anyway my immediate problem is solved. -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/zuBknMcgNe8RRjZUeHaFZWft_6YVlFeB6KtnrMGXdeP1UqtGi9uJ4oWNKbViLaQMN_3SBbyxzplsm68nzW5Ks9bt9_7gd5gqO0WQim_i_F8%3D%40protonmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Guide: Monero wallet/daemon isolation w/qubes+whonix
qubenix: > mk: >> One last thing, >> >> It should be noted that I still had to remove option >> "--p2p-bind-ip=127.0.0.1" to let monerod bind on 0.0.0.0 to make it work. >> >> Any security implication about this ? Does all traffic is still routed >> through Tor network ? Forgot to mention that there is no security problem to bind on 0.0.0.0. -- qubenix PGP: 96096E4CA0870F1C5BAF7DD909D159E1241F9C54 OTR: qube...@chat.freenode.net OTR: DFD1DA35 D74E775B 3E3DADB1 226282EE FB711765 -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/0dbc186f-4c46-fe6b-e8d7-3e66af1cddcc%40riseup.net. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Guide: Monero wallet/daemon isolation w/qubes+whonix
mk: > One last thing, > > It should be noted that I still had to remove option > "--p2p-bind-ip=127.0.0.1" to let monerod bind on 0.0.0.0 to make it work. > > Any security implication about this ? Does all traffic is still routed > through Tor network ? > If you are using gateway sys-whonix then all of your traffic is always using Tor. Not sure what you mean about "make it work", but I'm having some stalling/connection issues[1][2] on the newly released version (v0.13.0). At first connection issues were solved by adding torsocks to monerod when using Whonix gateway or binding p2p ip to 0.0.0.0 if not using a Whonix gateway. Next I started to experience stalls, which I still haven't found a solution for yet. [1] https://github.com/monero-project/monero/issues/4468 [2] https://github.com/monero-project/monero/issues/4469 -- qubenix PGP: 96096E4CA0870F1C5BAF7DD909D159E1241F9C54 OTR: qube...@chat.freenode.net OTR: DFD1DA35 D74E775B 3E3DADB1 226282EE FB711765 -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/c3466858-cc53-118b-3e79-11ef6de7c132%40riseup.net. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Guide: Monero wallet/daemon isolation w/qubes+whonix
One last thing, It should be noted that I still had to remove option "--p2p-bind-ip=127.0.0.1" to let monerod bind on 0.0.0.0 to make it work. Any security implication about this ? Does all traffic is still routed through Tor network ? -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/91426429-1b07-4206-8384-a1113254d9a5%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Changing USB Controllers
The laptop I have is a MSI WT70 20K. I have 5 USB ports total on it. Three USB3 ports and two USB2 ports. I have tryed making a sys-usb from the default settings and it crashes the install(probably because qubes is installed on a usb and its grabbing all the USB controllers). Installing without sys-usb works without any issues. following these instructions https://www.qubes-os.org/doc/assigning-devices/#finding-the-right-usb-controller i am seeing that all the ports I plug a USB storage device in use the same controller as my qubes OS (dom0) which is the XHCI controller. On Wed, Oct 10, 2018, 10:18 AM unman wrote: > On Mon, Oct 08, 2018 at 07:27:23PM -0700, Alex Winter wrote: > > Here are the usb controllers when I type in 'sudo lspci -v' > > > > 00:14.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset > Family USb xHCI (Rev 05) (prog-if 30 [XHCI]) > > Subsystem: Micro-Star International Co., Ltd. [MSI] Device 10ec > > Flags: bus master, medium devsel, latency 0, IRQ 57 > > Memory at f7b0 (64-bit, non-prefetchable) [size=64k] > > Capabilities: [70] Power Management version 2 > > Capabilities: [80] MSI: Enable+ Count=1/8 Maskable- 64bit+ > > Kernel driver in use: xhci_hcd > > Kernel modules: xhci_pci > > > > 00:1a.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset > Family USb EHCI #2 (Rev 05) (prog-if 20 [EHCI]) > > Subsystem: Micro-Star International Co., Ltd. [MSI] Device 10ec > > Flags: bus master, medium devsel, latency 0, IRQ 16 > > Memory at f7b18000 (32-bit, non-pcopy and pasterefetchable) [size=1k] > > Capabilities: [50] Power Management version 2 > > Capabilities: [58] Debug port: BAR=1 offset=00a0 > > Capabilities: [98] PCI Advanced Features > > Kernel driver in use: ehci-pci > > Kernel modules: ehci_pci > > > > 00:1d.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset > Family USb EHCI #1 (Rev 05) (prog-if 20 [EHCIReciever]) > > Subsystem: Micro-Star International Co., Ltd. [MSI] Device 10ec > > Flags: bus master, medium devsel, latency 0, IRQ 23 > > Memory at f7b17000 (32-bit, non-prefetchable) [size=1k] > > Capabilities: [50] Power Management version 2 > > Capabilities: [58] Debug port: BAR=1 offset=00a0 > > Capabilities: [98] PCI Advanced Features > > Kernel driver in use: ehci-pci > > Kernel modules: ehci_pci > > > > when I type in 'sudo lsusb -v' Here are the buses. > > > > Bus 002 Device 002: ID 8087:8000 Intel Corp. > > > > Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub > > iProduct 2 EHCI Host Controller > > iSerial 1 :00:1d.0 > > > > Bus 001 Device 002: ID 8087:8008 Intel Corp. > > > > Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub > > iproduct 2 EHCI Host Controller > > iSerial 1 :00:1a.0 > > > > Bus 004 Device 002: ID 04e8:61f5 Samsung Electronics Co., Ltd > > > > Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub > > iProduct 2 xHCI Host Controller > > iSerial 1 :00:14.0 > > > > Bus 003 Device 007: ID 1770:ff00 > > > > Bus 003 Device 005: ID 8087:07dc Intel Corp. > > > > Bus 003 Device 004: ID 045e:00e1 Microsoft Corp. Wireless Laser Mouse > 6000 receiver > > > > Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub > > iProduct 2 xHCI Host Controller > > iSerial 1 :00:14.0 > > > > Without knowing your laptop or exact setup I'm working a bit blind. > I think you say you have a usbVM and are running qubes from a USB stick > - is that right? > You haven't said *which* controller your ports all use. > > From the listing it's clear you have usb2 and usb3 controllers, and it > may be that ALL your ports are 2/3. More info needed please. > I'll throw out some wild suggestions: > > Hide one of the controllers on the kernel command line(say the xhci). > Disable ehci in usbVM, and use only USB3 devices with the usbVM. > > It might be possible to delete one of the devices in dom0, and still have > it available in qubes. (I mean literally rm /dev/bus/usb/001) > > You could unbind a pci device early in boot. I've done this with Xen > before, to have one port in dom0 and the rest available to xen-pciback, > but haven't tried it with Qubes. > > You could use udev to block two of the ports in dom0, so that they are > only available in the usbVM. > > unman > > -- > You received this message because you are subscribed to the Google Groups > "qubes-users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to qubes-users+unsubscr...@googlegroups.com. > To post to this group, send email to qubes-users@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/qubes-users/20181010141825.hstxmzkgm6sdh3x3%40thirdeyesecurity.org > . > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to
Re: [qubes-users] Watch Videos on Qubes 4.0
Black Beard wrote on 10/14/18 8:29 PM: Hey guys, i hope that someone can help. On my external HDD i have some Files in Iso Format. Qubes have a Video Player on board but i cant watch the Iso. What can i do? Is there maybe a tutorial to install the VLC Player? About a message i would be happy. Installation applications in a Qubes template works the same way as it does for the distribution in that template. So, for example, if you are using Fedora 28 templates, you'd follow the Fedora VLC installation instructions you find out there. For Debian templates you'd need to look for Debian VLC install instructions. Just remember to install it in the template, not the AppVM. -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/158f656d-4079-57d7-9d41-7a5113d60ae1%40danwin1210.me. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Watch Videos on Qubes 4.0
Hey guys, i hope that someone can help. On my external HDD i have some Files in Iso Format. Qubes have a Video Player on board but i cant watch the Iso. What can i do? Is there maybe a tutorial to install the VLC Player? About a message i would be happy. -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/9cdc5181-6146-47c1-b9cb-7ba7256b3e2d%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Guide: Monero wallet/daemon isolation w/qubes+whonix
Ok I see, Thanks again. -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/86544dde-c1a3-4851-82ee-62ff9aaa2b64%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Guide: Monero wallet/daemon isolation w/qubes+whonix
mk: > qubenix, > > I thought I had to run a full node to be synced with main blockchain but I > now understand that running a local node is enough > > So everything works as expected, > > Thanks for you answer and clarification :) > It's still a full node because you fully validate all transactions and blocks as they come in. You just don't send them to new nodes trying to sync. Glad it helped. -- qubenix PGP: 96096E4CA0870F1C5BAF7DD909D159E1241F9C54 OTR: qube...@chat.freenode.net OTR: DFD1DA35 D74E775B 3E3DADB1 226282EE FB711765 -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/ffc22c09-06c7-494e-baea-7d09af6a3113%40riseup.net. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Guide: Monero wallet/daemon isolation w/qubes+whonix
qubenix, I thought I had to run a full node to be synced with main blockchain but I now understand that running a local node is enough So everything works as expected, Thanks for you answer and clarification :) -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/db4fabed-bc02-47c4-87bb-2e1a1110a58e%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: If you get "no authenticators available" with mutt
On Friday, February 9, 2018 at 11:02:21 PM UTC+5:30, Konstantin Ryabitsev wrote: > If you are trying to use mutt with the default Fedora-26 template and > can't figure out why authenticated smtp sending is giving you a "No > Authenticators Available" error, you need to install cyrus-sasl-plain. > > Drove me half-mad before I figured that out. Hopefully it saves you a > bunch of clicks (and hair). > > -K THanks man! saved a lot of time! -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/eb91b8c6-9579-4981-afd1-85fdc2c82073%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: If you get "no authenticators available" with mutt
On Friday, February 9, 2018 at 11:02:21 PM UTC+5:30, Konstantin Ryabitsev wrote: > If you are trying to use mutt with the default Fedora-26 template and > can't figure out why authenticated smtp sending is giving you a "No > Authenticators Available" error, you need to install cyrus-sasl-plain. > > Drove me half-mad before I figured that out. Hopefully it saves you a > bunch of clicks (and hair). > > -K Any reason as to why installing this package worked? -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/b28f5f59-d192-4716-837f-4fd46d86fd91%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Guide: Monero wallet/daemon isolation w/qubes+whonix
mk: > Hi guys, > > Thanks for your work on this. > > Setup is working fine for me except that I could not find a way to properly > forward i2p port (18080) from outside to monerod-ws when using sys-whonix as > the netVM, I had to switch to sys-firewall. >> (Script used to setup port forward https://gist.github.com/Joeviocoe/6c4dc0c283f6d6c5b1a3f5af8793292b) > > any ideas on how to fix this ? > It's not i2p port, it's the p2p (peer to peer) port. 1. You don't need to open that port unless you want to. It's only used for serving blocks and transactions to other nodes. Monero's documentation suggests to not open that port when using Tor. Not to be confused with the rpc port (18081), which is opened when wanting to create a remote node for light clients to connect to. 2. If you want to keep using sys-whonix as NetVM (better for privacy), and you still want to open the port, use a Tor hidden service: https://whonix.org/wiki/Hidden_Services. You'll just have to advertise your onion address out of band somehow because Monero doesn't have a setting like externalip= to let peers know about your onion. Probably not worth it. 3. If you want to use sys-firewall you'll have to remove the p2p-bind-ip=127.0.0.1 from the /lib/systemd/system/monerod.service file on the TemplateVM. You will probably also have to allow the port forward on your home router somehow. -- qubenix PGP: 96096E4CA0870F1C5BAF7DD909D159E1241F9C54 OTR: qube...@chat.freenode.net OTR: DFD1DA35 D74E775B 3E3DADB1 226282EE FB711765 -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/5e2c15c7-e5b1-5ae0-187e-22cc2adca019%40riseup.net. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Guide: Monero wallet/daemon isolation w/qubes+whonix
Hi guys, Thanks for your work on this. Setup is working fine for me except that I could not find a way to properly forward i2p port (18080) from outside to monerod-ws when using sys-whonix as the netVM, I had to switch to sys-firewall. (Script used to setup port forward https://gist.github.com/Joeviocoe/6c4dc0c283f6d6c5b1a3f5af8793292b) any ideas on how to fix this ? -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/1eac69c2-e219-41fc-bd0b-08a02586f9d1%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Post-install inability to create qube
On 10/12/2018 01:44 AM, 'awokd' via qubes-users wrote: newpa...@gmail.com wrote on 10/12/18 5:37 AM: Hello, After completing install (for my first time), I was able to login. Going to the menu, "Create Qubes VM," getting the dialog box titled "[Dom0] Create new qube," the Template select drop-down control only has "default(none)," even if I select type Standalone rather than AppVM. Also, I don't see anything anywhere like work, personal and untrusted, neither sys-net or sys-usb. /var/lib/qubes/vm-templates has a debian and fedora folder, but it seems like these are not available when trying to create qubes via CLI via qvm-create. journalctl all show an AssertionError. Any ideas? Did you receive any errors on the first post-install boot? There's a step there that is supposed to configure all those templates. Is it possible you skipped it? Otherwise, often a misbehaving network device causes sys-net creation to break, which then causes the rest to fail to get created. In that case, try disabling your wifi card temporarily, then reinstalling. You can re-enable it afterwards and add it back to your sys-net in Qube Settings/Devices. Try 'sudo dnf list qubes-template*' to see a list of installed templates. If there are none, try mounting the installation media, locate a qubes-template*rpm file and install the rpm file directly. This should be a lot less time-consuming than re-installing Qubes. -- Chris Laprise, tas...@posteo.net https://github.com/tasket https://twitter.com/ttaskett PGP: BEE2 20C5 356E 764A 73EB 4AB3 1DC4 D106 F07F 1886 -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/03a9bdf6-2506-2b8f-ce6e-623ec43acde1%40posteo.net. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] traveling change time how ?
Hi, reby: > I guess it should be evident but apparently not ? I've changed the timezone > manually on the taskbar to the new TZ , however I see that when I update a > Template it is still using my home TZ not my current TZ > > > what are the steps to correctly change to a new TZ when travelling with Q4.0 > and a laptop please ? You should be able to change the timezone with the `timedatectl` tool in dom0. An example to set the system timezone Europe/London: # sudo timedatectl set-timezone 'Europe/London' For time changes to take effect in other VMs be sure to restart them after updating the time or perhaps there is a better that I'm unaware of. Cheers, ~Vasilis -- Fingerprint: 8FD5 CF5F 39FC 03EB B382 7470 5FBF 70B1 D126 0162 Pubkey: https://pgp.mit.edu/pks/lookup?op=get=0x5FBF70B1D1260162 -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/45638198-11a8-12be-a345-e84e166ab6f4%40torproject.org. For more options, visit https://groups.google.com/d/optout. signature.asc Description: OpenPGP digital signature
Re: [qubes-users] My touchpad and mouse didn't work
On Sat, 13 Oct 2018 13:13:58 -0700 (PDT) Máté Kovács wrote: >Hi >Somehow I turned off my touchpad in Qubes, and it get stucked in the middle of >the screen. >How can I navigate myself to dom0 console with my notebook's keyboard? > For a command line console, ctl-alt-F2 (or F3,4,5,6,7) and login with the admin account. You can do whatever you can do from a command line except start a graphical program. Stuart -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/20181014074753.64644927%40gmail.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: HCL - Thinkpad X1 Carbon 6th gen - Qubes 4.0
On Tuesday, 17 April 2018 00:14:43 UTC+2, fiasc...@gmail.com wrote: > Summary: Install worked reasonably well and it boots with EFI into the > installed Qubes 4.0 nicely. There are a few issues to resolve. > > 1. I have the model with a touch screen and I haven't debugged how to make it > work yet (I'll get to that and post back what worked). > > 2. Suspend/resume doesn't work and I have to do a hard reset. A few times > (not all) I had to hard reset twice to get it to reboot properly. > > 3. HCL reports no TPM, but I have a dTPM 2.0. > > It's booting with UEFI smoothly. I haven't tested the mic, camera, or ports > except USB for storage yet. I'll update once I find fixes for the above. If > anyone could point me in the right direction for the suspend freezing issue, > let me know. I tried shutting down all VMs, including service VMs after > reading this, > https://groups.google.com/d/msg/qubes-users/81t26xq4MEI/HrfDEcjeAgAJ but the > problem persisted didn't change anything. Did anyone try throttling / thermal fix described here https://github.com/erpalma/lenovo-throttling-fix ? -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/71c958cb-cdd0-4599-8517-32fce8f8bbe8%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: My touchpad and mouse didn't work
On 10/14/18 10:39 AM, Máté Kovács wrote: 2018. október 13., szombat 22:13:58 UTC+2 időpontban Máté Kovács a következőt írta: Hi Somehow I turned off my touchpad in Qubes, and it get stucked in the middle of the screen. How can I navigate myself to dom0 console with my notebook's keyboard? I made a huge mistake when I tried at the settings how to set up my usb mouse, and I accidentally turned off the touchpad after the arrow of my mouse somehow moved a few millimeters away, and I cannot re enable it again. :/ CTRL-ESC should show the qubes menu; use arrows to go into system tools -> mouse and touchpad, and use arrows/tab/space to change the settings. Or do you mean that you already did that but that the touchpad is still disabled ? If so, make sure it is really enabled (as above) and reboot. -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/29e9682c-012c-66f6-77e5-2e5d6821526d%40maa.bz. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: My touchpad and mouse didn't work
2018. október 14., vasárnap 8:21:10 UTC+2 időpontban Ivan Mitev a következőt írta: > On 10/14/18 8:39 AM, Hugo Costa wrote: > > On Saturday, 13 October 2018 21:13:58 UTC+1, Máté Kovács wrote: > >> Hi > >> Somehow I turned off my touchpad in Qubes, and it get stucked in the > >> middle of the screen. > >> How can I navigate myself to dom0 console with my notebook's keyboard? > > > > I usually just restart the computer when something like that happens. But > > in your case, I'd probably just alt tab into the Qube Manager and go on > > from there. > > I also had a stucked pointer a few times for the past 2-3 weeks - don't > know what is triggering it. Instead of rebooting you could try to login > in a text console (eg ctrl-alt-2) and suspend the laptop (`systemctl > suspend`). After resuming I could move the pointer again, maybe it'll > work for you and the OP - rebooting is really painful/slow. At where and when can I login in the text console? After I restarted my computer? Before it asks the disk passphrase? -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/5ed1fb55-4271-4fbb-b67e-7b3ce105636e%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: My touchpad and mouse didn't work
2018. október 13., szombat 22:13:58 UTC+2 időpontban Máté Kovács a következőt írta: > Hi > Somehow I turned off my touchpad in Qubes, and it get stucked in the middle > of the screen. > How can I navigate myself to dom0 console with my notebook's keyboard? I made a huge mistake when I tried at the settings how to set up my usb mouse, and I accidentally turned off the touchpad after the arrow of my mouse somehow moved a few millimeters away, and I cannot re enable it again. :/ -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/faed73ff-30f3-40f2-8e1e-0bbbd64be7cf%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: My touchpad and mouse didn't work
On 10/14/18 8:39 AM, Hugo Costa wrote: On Saturday, 13 October 2018 21:13:58 UTC+1, Máté Kovács wrote: Hi Somehow I turned off my touchpad in Qubes, and it get stucked in the middle of the screen. How can I navigate myself to dom0 console with my notebook's keyboard? I usually just restart the computer when something like that happens. But in your case, I'd probably just alt tab into the Qube Manager and go on from there. I also had a stucked pointer a few times for the past 2-3 weeks - don't know what is triggering it. Instead of rebooting you could try to login in a text console (eg ctrl-alt-2) and suspend the laptop (`systemctl suspend`). After resuming I could move the pointer again, maybe it'll work for you and the OP - rebooting is really painful/slow. -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/22398a2d-abad-820d-95bd-46eb68255335%40maa.bz. For more options, visit https://groups.google.com/d/optout.
