[qubes-users] Re: ThinkPad X270 USB C/Thunderbolt USB C type and docking station Qubes 4.0
onsdag den 20. marts 2019 kl. 13.33.27 UTC+1 skrev a...@it-minds.dk: > Hello qubes users! > > I currently acquired this dock > (https://www.dell.com/en-us/shop/dell-business-thunderbolt-dock-tb16-with-240w-adapter/apd/452-bcnu/pc-accessories), > and tried to connect it with my laptop, but it does not seem to work. > > I have found different posts here and there regarding the issue, and I think > the most common solution is turning on the computer with the cable attached. > This does NOT work however. > > I have not tried to boot up without attaching, and viewing lspci output, and > then comparing to when I have it connected. Will do that and post back if > there are no better suggestions for now. > > I have also NOT modified my kernel yet or done anything to the start up flags > (other than enabling USB devices in general, so I can use my keyboard and > mouse). > > I am running Qubes 4.0. > > Any help appreciated! > > Best regards! To future readers who own a ThinkPad X270: There is a USB C port, but it is NOT a Thunderbolt port. There was never any chance of getting the dock to work. If you want a ThinkPad X class with Thunderbolt, it should be in the X280 series and upwards probably. Thank you everybody for your time and for pitching in. Sorry for not doing my research before posting here. Best regards! -- 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/be95e2b1-42b1-4912-8d4a-a46c744fdab2%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: ThinkPad X270 USB C/Thunderbolt USB C type and docking station Qubes 4.0
torsdag den 21. marts 2019 kl. 11.34.10 UTC+1 skrev David Hobach: > > True, that is somewhat more advanced though. State-level attackers have > teams that can open and replace arbitrary hardware with malicious one > within 15 mins, yes. So if you fear them, don't leave your laptop > unattended anyway. > In contrast your colleague sitting next to you at work can plug in a USB > stick into your laptop and perform the thunderbolt attack whilst you're > at lunch. > Having someone physically take away your laptop or even dismantle it is > a lot more suspicious. > > Qubes OS is focusing on security and fortunately doesn't make security > tradeoffs even for usability. > > [1] http://thunderclap.io/ I have to say that I agree with Matthew on this. It seems kind of over the top, especially with no way to at least accept the risk and enable it anyway. Making it work the same as with USB devices seems like a good way to do this (without trying to make this issue trivial, it genuinely seems like a major pain point to design a proper solution and I completely respect that). I just think it seems overkill to not even have an option to enable it. I don't doubt at all that there are people out there who would be exposed if this was enabled by default, so I definitely respect and understand that. We are however able to enable USB support and exposure to dom0 when wanting to use a USB keyboard for instance. There is a fine warning in the documentation about it, so you as a user, know exactly what risk you are taking by doing so. If you are hired a place where you can use Qubes OS as your main OS, and you have colleagues who something like that, then I would maybe argue there is something inherently wrong with the working environment, but you are correct at any rate. I do not agree with the premise though! I will try out what Matthew suggested. Otherwise I guess I will just have to wait it out. Shame I didn't research better before I invested in it though :( Thank you for your input! -- 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/0c0512a5-bc36-426a-890a-5feb8801d2b2%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] ThinkPad X270 USB C/Thunderbolt USB C type and docking station Qubes 4.0
Hello qubes users! I currently acquired this dock (https://www.dell.com/en-us/shop/dell-business-thunderbolt-dock-tb16-with-240w-adapter/apd/452-bcnu/pc-accessories), and tried to connect it with my laptop, but it does not seem to work. I have found different posts here and there regarding the issue, and I think the most common solution is turning on the computer with the cable attached. This does NOT work however. I have not tried to boot up without attaching, and viewing lspci output, and then comparing to when I have it connected. Will do that and post back if there are no better suggestions for now. I have also NOT modified my kernel yet or done anything to the start up flags (other than enabling USB devices in general, so I can use my keyboard and mouse). I am running Qubes 4.0. Any help appreciated! Best regards! -- 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/d04203ef-1898-440b-9ff5-8863aebb14f2%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Qubes 4 crashes
Hello! I have experienced a couple of times now that my Qubes 4 installation crashes at different times. I do not expect this to be an issue with Qubes, but it would be nice if I could debug this some how. I have no idea where to look for the necessary logs though. Some details: The crash itself comes in different forms, but the outcome is always the same; total system freeze where a hard shutdown is required. Often it crashes with some kind of graphical glitch where the GUI is skewed. I.e. colours look weird and it is obvious that the screen glitched. Yesterday I experienced that it crashed without glitching though, so it took me some time to realise that it was actually crashed. It usually happens when my laptop is running on battery. I have never experienced it when it is plugged into the charger. I have a Thinkpad X270, i7 processor, 8 GB RAM. I am personally suspecting a lack of RAM maybe, but I need to have it confirmed by others or get another opinion. Thank you very much! -- 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/0b22d136-b883-4e59-a5fe-2d5bcf816ade%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Installed KDE, removed KDE, now lightdm and startx are broken
onsdag den 5. december 2018 kl. 15.45.33 UTC+1 skrev Ranguvar: > On Wed, Dec 5, 2018 at 3:56 AM aaq via qubes-users > wrote: > tirsdag den 4. december 2018 kl. 23.46.32 UTC+1 skrev Ranguvar: > > > On Tue, Dec 4, 2018 at 5:41 PM wrote: > > > Hey all! > > > > > > Using Qubes 4.0.1-rc1, been updating with qubes-dom0-update --releasever=4.0 > > > I installed @kde-desktop-qubes, and then later uninstalled it. > > > This seems to have ripped out lightdm and some other parts of X/Xfce. > > > Now I don't have lightdm to login, and startx fails to load any video > > driver. > > > > > > I can't seem to reinstall @xfce-desktop-qubes or similar. > > > > > > Any way to find all RPMs included in that group and download on another > > machine to pass to the Qubes partition after opening with cryptsetup? > > > > > > Or, any other solution to this seem apparent? > > > > > > Thanks! > > > > > > - Devin > > > > > > > > > `startxfce4` allows me to get a graphical display up, but then I > > completely lose all input. > > > > Hello! > > > > If you have access to your machines CLI, then you should be able to reinstall > the packages through dnf. That is all of @kde-desktop-qubes. After that, you > can removing different parts again. > > > > I also installed KDE, and realised that I did not want it, but I noticed how > much dnf wanted to remove so I just stuck with it (and am actually using KDE > mainly now). > > > > I am sorry I cannot give you more clear directions.. > > > > Thanks! > > Unfortunately, I cannot install any packages from inside Qubes. > This seems to have broken the Internet connection that the net VM uses, or > the connection from net VM to dom0. You should not need a network connection to install from cache in dom0. I do not remember the exact command, but reading the man page for dnf should provide some insight. -- 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/7c1f93cb-b9b6-4e48-b185-6dc4c6a249f5%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Installed KDE, removed KDE, now lightdm and startx are broken
tirsdag den 4. december 2018 kl. 23.46.32 UTC+1 skrev Ranguvar: > On Tue, Dec 4, 2018 at 5:41 PM wrote: > Hey all! > > > > Using Qubes 4.0.1-rc1, been updating with qubes-dom0-update --releasever=4.0 > > > > I installed @kde-desktop-qubes, and then later uninstalled it. > > > > This seems to have ripped out lightdm and some other parts of X/Xfce. > > > > Now I don't have lightdm to login, and startx fails to load any video driver. > > > > I can't seem to reinstall @xfce-desktop-qubes or similar. > > > > Any way to find all RPMs included in that group and download on another > machine to pass to the Qubes partition after opening with cryptsetup? > > > > Or, any other solution to this seem apparent? > > > > Thanks! > > > > - Devin > > > > `startxfce4` allows me to get a graphical display up, but then I completely > lose all input. Hello! If you have access to your machines CLI, then you should be able to reinstall the packages through dnf. That is all of @kde-desktop-qubes. After that, you can removing different parts again. I also installed KDE, and realised that I did not want it, but I noticed how much dnf wanted to remove so I just stuck with it (and am actually using KDE mainly now). I am sorry I cannot give you more clear directions.. -- 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/81768d55-b5e8-4ee4-a113-ac2881a16c98%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: Recovering TemplateVM from boot failure caused by incorrect /etc/fstab
mandag den 26. november 2018 kl. 12.46.29 UTC+1 skrev fabio_p7cc62u: > I made an accidental edit to /etc/fstab which is causing my TemplateVM to > timeout on boot with error Cannot connect to qrexec agent for 60 seconds > > Is there a way to edit a particular VM's etc/fstab without booting it up? Can > I perhaps mount it's root filesystem? > Attempted solutions > > 1. I've tried adding init=/bin/bash to the kernel opts, starting the > templateVM and then running sudo xl console TEMPLATE_NAME from Dom0 but I did > not reach a command-prompt before fstab was read and executed. > > > > 2. I tried mounting the root filesystem for the TemplateVM from Dom0 with: > sudo mount /dev/qubes_dom0/vm-fedora-26-root mnt but got error wrong fs type, > bad option, bad superblock... > > Any suggestions on how I could edit /etc/fstab for my TemplateVM before it > gets executed? > Steps to reproduce the behavior: > Edit your /etc/fstab to be incorrectly formatted > Run qvm-start YOUR_FAULTY_TEMPLATE > > > > Related issue: > https://unix.stackexchange.com/questions/44027/how-to-fix-boot-failure-due-to-incorrect-fstab Hello! Please this issue: https://groups.google.com/forum/#!topic/qubes-users/rWRNIt0NOc4 Hope this helps :) -- 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/8824b60f-afb7-499c-94e8-4e269e55180c%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: Change update Template from sys-whonix to sys-whonix-New
mandag den 19. november 2018 kl. 16.55.42 UTC+1 skrev 22...@tutamail.com: > I recreated a new Appvm for my templates to use for updates. I currently use > sys-whonix...the new template is sys-whonix-New. > > > How would I do this? Hey there! I am not currently on my Qubes box, but I guess you can change it in the Qubes Global Settings program (if you want GUI). I am pretty sure you can set the dom0 update VM in there. Otherwise you can also do it with qvm-prefs, I just don't have enough experience using it to set stuff on dom0. Hope this helps. -- 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/14f925a0-a2dc-4731-bc94-c4ca78f585a2%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: How to Change Default Language Qubes 4
søndag den 18. november 2018 kl. 17.00.19 UTC+1 skrev Campbell: > On install I chose UK English with US Keyboard. For some reason upon > installation Qubes set my laptop keyboard to UK, even though I chose US > keyboard during installation. > > My guess is that when Qubes set language to UK English it automatically set > the keyboard to UK, despite what I entered at install. > > How do I change the default language to US English, and will that fix my > keyboard layout? Hello! If you aren't going to use any other keyboard layouts than US, then look into setting it on X server level. That's what I do at least. Look here: https://wiki.archlinux.org/index.php/Xorg/Keyboard_configuration#Using_X_configuration_files Basically you need to add a file in /etc/X11/xorg.conf.d/ in dom0 (it doesn't really matter what you call the file, as long as you don't have clashing files). For US layout the file would look something like: Section "InputClass" Identifier "Keyboard Defaults" MatchIsKeyboard "yes" Option "XkbLayout" "us" EndSection hope this helps! -- 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/aecf7210-c67a-40a0-a96e-7966edd4315d%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: i3 wm package still in testing
lørdag den 17. november 2018 kl. 23.44.01 UTC+1 skrev Vasilis: > Hi, > > It seems that the i3 window manager has been in the testing repository for a > while, and I don't see many bug reports or posts on the mailing lists with > problems associated to the i3 window manager. > > Anything else required to make this package stable or when it can be moved to > the stable repository? Hello! What version of Qubes are you running? I installed i3 directly through "sudo qubes-dom0-update i3" and that resolved fine. Even the patched settings too. So it should be in stable already. Regards -- 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/d1e9c3c0-950c-4986-857d-e9005a88e367%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: Qubes 4.0 +Debian9 with Chuckoo Sandbox on Virtualbox
lørdag den 17. november 2018 kl. 22.26.00 UTC+1 skrev Black Beard: > Hey community, > > i hope, that someone can help me by following probleme. > > My main OS is Qubes 4.0. No Dual-boot or other stuff. Only Qubes 4.0 > installed. > > My target: > > Install Chuckoo Sandbox in Virtualbox on Debian9 Hey! To my knowledge, it is not possible to run Virtualbox in a PVH VM (i.e. any type of Qube). You can create a HVM, but I don't know whether or not Virtualbox works in those. I would recommend installing Windows directly in a HVM though. I believe that's the recommended way from the Qubes devs as well. Full disclosure: I don't know what Cuckoo is or how it works. Hope you can use this :) Otherwise, maybe someone else can chime in! Regards -- 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/f32c995f-8694-478c-a9d2-5ace268ffd5d%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Qubes 3.2 whonix 14 connects to tor, but there is no connection
lørdag den 17. november 2018 kl. 17.01.02 UTC+1 skrev Patrick Schleizer: > Franz: > > I succesfully updated to whonix 14, when the VM start a message tells: > > "connected to tor" making me happy, But if I ping google I get: > > > > user@host:~$ ping google.com > > PING google.com (216.58.207.206) 56(84) bytes of data. > >>From 10.137.5.34 (10.137.5.34) icmp_seq=1 Destination Port Unreachable > > ping: sendmsg: Operation not permitted > > > > > > what may be wrong? > > Best > > > > ping is UDP. And Tor doesn't support UDP. > > https://www.whonix.org/wiki/Tor#UDP Ping is ICMP, not UDP. https://en.wikipedia.org/wiki/Internet_Control_Message_Protocol -- 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/17fcb785-71a9-4513-abfe-ff63a3a1de79%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] sys-net and KDE
Hello! So, I switched to KDE as you can see in some other threads, and honestly I like it way better than XFCE. My biggest issue right now however is, that the network manager applet does not show in KDE. I get notification when I start my session that I am connected to my network, and I do have connectivity. I am however not able to use the applet to connect to new networks or generally initiate network manager related actions. I run Qubes 4.0.0, and my sys-net runs the fedora-28 template (without modifications). I have tried googling around but could not seem to find a solution. I found an old fedora thread stating that there is a package that can be used for network manager in KDE (I can't seem to find it again). That package didn't work however. I have tried opening a terminal in sys-net, killing nm-applet and starting it again. That does not seem to work either. Any comments/suggestions welcome! Thanks in advance! -- 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/018a4e3f-12b4-49e2-923c-e5e16e599bf8%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Broken GUI Qubes 4
tirsdag den 13. november 2018 kl. 12.26.58 UTC+1 skrev unman: > On Tue, Nov 13, 2018 at 12:00:40AM -0800, aaq via qubes-users wrote: > > Hello! > > > > I have broken the GUI in dom0 in some weird way. > > I tried to install KDE, then I tried to remove it again, before realising > > that I was fine with having it. Unfortunately, when I wanted to reinstall > > it, dnf kept saying that I already had the group installed, so I couldn't > > just run the `sudo qubes-dom0-update @kde-desktop-qubes`. > > > > I ended up doing a `sudo dnf remove @kde` in dom0, which resulted in the > > package `qubes-gui-dom0` being deleted. I assume this is the package that > > is needed to show GUI from different VMs. > > > > Basically, dom0 works fine. All of dom0 GUI works as intended, I am happily > > using KDE and SDDM. With that being said, none of my VMs work, so I can't > > really use my machine for anything. > > > > I found this thread > > https://groups.google.com/forum/#!topic/qubes-users/7GeA1_xCeTg > > > > But I cannot start VMs with `--no-guid` flag. I cannot for the love of my > > life get the package back.. I haven't cleared my cache or anything, but for > > some reason I am not able to install `qubes-gui-dom0` again without a > > network connection. Since my VMs don't start properly, I don't have network. > > > > Is there any solution to this :S > > > > PS: I backed up all my VMs the other day (happy coincidence) so I guess I > > could just reinstall, but I am quite happy with my current install :( > > > > Thanks for any input! > > > > The obvious solution would be to download the files in another machine > and then transfer them to dom0 using a transfer disk. > If you're on a laptop and have a sys-usb set up then you will need to > interrupt boot and edit the kernel parameters to remove the section that > says rd.qubes.hide_all_usb - that will allow you to connect USB to > dom0 at some cost to your security. > > If you dont want to do that we can try troubleshooting your inability > to start headless qubes. > If you wnat to do that then try starting just sys-net from the command > line and check the logs, and report back any error from the logs or > command line. Thank you so much for you time! When having all Qubes shutdown, I run qvm-start --verbose sys-net No feedback in the terminal. I cannot seem to find anything in the logs that might seem interesting either. I don't know if I am looking the wrong places. I looked into /var/logs/qubes/ and then anything with sys-net in it. I also looked at the xen logs for the VM, but again, I can't seem to find anything special that stands out. -- 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/5f1921d0-3bdd-422b-ab29-2e577e893d3b%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Broken GUI Qubes 4
Hello! I have broken the GUI in dom0 in some weird way. I tried to install KDE, then I tried to remove it again, before realising that I was fine with having it. Unfortunately, when I wanted to reinstall it, dnf kept saying that I already had the group installed, so I couldn't just run the `sudo qubes-dom0-update @kde-desktop-qubes`. I ended up doing a `sudo dnf remove @kde` in dom0, which resulted in the package `qubes-gui-dom0` being deleted. I assume this is the package that is needed to show GUI from different VMs. Basically, dom0 works fine. All of dom0 GUI works as intended, I am happily using KDE and SDDM. With that being said, none of my VMs work, so I can't really use my machine for anything. I found this thread https://groups.google.com/forum/#!topic/qubes-users/7GeA1_xCeTg But I cannot start VMs with `--no-guid` flag. I cannot for the love of my life get the package back.. I haven't cleared my cache or anything, but for some reason I am not able to install `qubes-gui-dom0` again without a network connection. Since my VMs don't start properly, I don't have network. Is there any solution to this :S PS: I backed up all my VMs the other day (happy coincidence) so I guess I could just reinstall, but I am quite happy with my current install :( Thanks for any input! -- 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/4a0f5ceb-2f24-42a4-beb0-2c4b335d5c46%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: Updated Debian template-Recieved "Configuring grub-pc" message??
mandag den 12. november 2018 kl. 03.10.59 UTC+1 skrev 22...@tutamail.com: > Thank you both for the comments... > > In the message I remember a statement: "..This menu allows you to > select...automatic run for, if any...running grub-install automatically is > recommended". I believe it also said something to the effect: "...will use > the previous selection..." > > Considering I already completed the update and everything is working should I > be concerned? Would anything bad already have happened? Next time I'll pick > try the "/dev/xvda" file and see what happens but does it default to the same > selection as prior to the upgrade when nothing is selected? > > Thanks again... If your TemplateVM/AppVM/StandaloneVM is able to start up, after you have done the upgrade then I don't think you should be concerned. Just keep in mind in the future, that you should use /dev/xvda as your device for grub :) -- 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/cdb493ad-0ad1-4cb4-bd09-44a51d10ef7d%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: Removing KDE
mandag den 12. november 2018 kl. 01.03.18 UTC+1 skrev unman: > On Sun, Nov 11, 2018 at 09:54:08AM -0800, aaq via qubes-users wrote: > > søndag den 11. november 2018 kl. 17.17.27 UTC+1 skrev a...@it-minds.dk: > > > Hello everybody! > > > > > > I wanted to try out KDE with Qubes 4, but found that it was simply too > > > much compared to my needs. > > > > > > Unfortunately, removing KDE again isn't as simple as installing it. My > > > biggest issues is that it hijacked some core components across the > > > system, even though I am not using KDE (such as the notification frontend > > > among other things). > > > > > > I found an old thread where Marmarek suggested using `dnf mark install` > > > on the packages that dnf wrongly tries to remove, but dnf remains way too > > > aggressive in what it wants to remove. > > > > > > Basically dnf wants to remove everything X related, not only the KDE > > > stuff installed. > > > > > > If anybody knows any way of reverting and purging KDE completely, I would > > > be eternally grateful! > > > > > > Otherwise I might just have to backup all my stuff and go for a reinstall > > > :( > > > > > > Thanks in advance! > > > > > > PS: Lesson has been learned.. don't mindlessly install unncessary things. > > > Thanks. > > > > So.. > > > > I ended up deleting most of the packages (if not all) by hand. > > Unfortunately, my system is in a limbo mode right now. The notification > > front end still looks weird (in dom0), and my lightdm is presented with a > > black background. Other than that, my system works fine. > > Kind of annoying in this state, but works. My OCD is just getting the best > > of me :) > > > > It would be nice with some comments in the documentation on the website > > about KDE being hard to revert from, or at least some specific instructions > > on how to revert. I would be more than happy to contribute with that, but I > > am going to need some help with the steps needed. > > > > Hope someone will chime in! > > The simplest way to remove (most of) KDE is, I think: > dnf remove kdelibs,plasma-workspace > > Removing those packages pulls out those that depend on them while > leaving Xfce (and X) untouched. > > Though why you would want to remove Plasma? So easy to configure and > customize, and really enhances Qubes experience. > > unman Honestly I completely agree. If I was to use a DE I would definitely prefer KDE or GNOME over XFCE (I sincerely hate XFCE, loose opinion held strongly). I am however an avid user of i3, and since most of my stuff is opened and configured through templatevm/standalonevm, I don't really have a particular need for a heavy dom0 DE. My machine only has 8 gb of RAM, and so far that is more enough for my usage, but I fear if I bloat dom0 too much, that I might end up having some issues.. My biggest issue right now is, that after I installed KDE and logged in to Plasma, it didn't correctly override all the XFCE/gtk stuff. So my machine was in a state where it started up some things from kde and some stuff from xfce. That was obviously completely unwanted behavior.. If you have some guidelines though, as to how I can switch off xfce stuff and turn completely to the dark side, I mean KDE, then I would appreciate your time. Thank you! Regards! -- 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/9f551631-973e-4816-8907-eaf574b377be%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: Removing KDE
søndag den 11. november 2018 kl. 17.17.27 UTC+1 skrev a...@it-minds.dk: > Hello everybody! > > I wanted to try out KDE with Qubes 4, but found that it was simply too much > compared to my needs. > > Unfortunately, removing KDE again isn't as simple as installing it. My > biggest issues is that it hijacked some core components across the system, > even though I am not using KDE (such as the notification frontend among other > things). > > I found an old thread where Marmarek suggested using `dnf mark install` on > the packages that dnf wrongly tries to remove, but dnf remains way too > aggressive in what it wants to remove. > > Basically dnf wants to remove everything X related, not only the KDE stuff > installed. > > If anybody knows any way of reverting and purging KDE completely, I would be > eternally grateful! > > Otherwise I might just have to backup all my stuff and go for a reinstall :( > > Thanks in advance! > > PS: Lesson has been learned.. don't mindlessly install unncessary things. > Thanks. So.. I ended up deleting most of the packages (if not all) by hand. Unfortunately, my system is in a limbo mode right now. The notification front end still looks weird (in dom0), and my lightdm is presented with a black background. Other than that, my system works fine. Kind of annoying in this state, but works. My OCD is just getting the best of me :) It would be nice with some comments in the documentation on the website about KDE being hard to revert from, or at least some specific instructions on how to revert. I would be more than happy to contribute with that, but I am going to need some help with the steps needed. Hope someone will chime in! -- 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/33f5c6e7-54f2-4881-9959-0d17a2ead94e%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: Updated Debian template-Recieved "Configuring grub-pc" message??
søndag den 11. november 2018 kl. 18.28.06 UTC+1 skrev 22...@tutamail.com: > I just updated my Debian template and received a "Configuring grub-pc" window > in my terminal, through trial and error I discovered that I was able to > select "OK", and select configurations using the curser arrows and the space > bar (->, <-, etc...). > > I haven't seen this on a Debian update before but I had the option to select > what I think are devices for grub-install...maybe 4 choices. I used the space > bar and selected all of them but then received error messages. I then > selected none of the options(devices?) and the update continued. The update > appeared to just continue finishing with "Press enter to shutdown...", no > obvious error messages like past template updates. Everything appears to be > working despite what appeared to be scary warnings in the terminal. > > Restarted the computer...no issues. Sorry to not have more info I wish I had > taken screen shots. > > Was I supposed to select something? Any way to check? What was the window? > > I am using 4.0... > > Thanks again, > 22rip Hello! This is fairly common when upgrading the kernel in Debian. In Qubes OS there are multiple mounts inside each Qube, and thus apt-get asks you where / or /boot is mounted, so that it knows where to upgrade grub. To my understanding (without having looked into it any further), I have kept guessing that the / dir is mounted in what is called /dev/xvda inside the Qube. I generally always mark that, and then it happily continues without any angry warnings. Would welcome any clarification too though :) Those are my 2 cents at least! Regards -- 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/6dc9c7f9-11a6-4a22-9129-9c7b8a927067%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Removing KDE
Hello everybody! I wanted to try out KDE with Qubes 4, but found that it was simply too much compared to my needs. Unfortunately, removing KDE again isn't as simple as installing it. My biggest issues is that it hijacked some core components across the system, even though I am not using KDE (such as the notification frontend among other things). I found an old thread where Marmarek suggested using `dnf mark install` on the packages that dnf wrongly tries to remove, but dnf remains way too aggressive in what it wants to remove. Basically dnf wants to remove everything X related, not only the KDE stuff installed. If anybody knows any way of reverting and purging KDE completely, I would be eternally grateful! Otherwise I might just have to backup all my stuff and go for a reinstall :( Thanks in advance! PS: Lesson has been learned.. don't mindlessly install unncessary things. Thanks. -- 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/4571758c-44c7-4e50-993b-a123a7f16ee4%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: i3 under Qubes 4 RC3
Den torsdag den 25. januar 2018 kl. 20.17.48 UTC+1 skrev Kevin Martinsen: > i3 has been working fine for me. > > Did you follow the installation instructions on > https://www.qubes-os.org/doc/i3/? Specifically: > $ sudo qubes-dom0-update --enablerepo=qubes-dom0-current-testing > i3-settings-qubes Yesh, I have followed those steps (but please also note that the documentation is related to 3.2, and as such it might be that i3 has actually been bumped to the stable repos, but I don't know :) > What do you mean you cannot start any programs from vms? How are you trying > to start programs? For me I have mod4+d to use dmenu. And do you mean to say > that qvm-run works correctly? My dmenu is broken, for starters. Dmenu only shows dom0 applications, so I cannot start anything that way. When I run qvm-run to start something, I can see that my VM is started (with qvm-ls) and I can hear my CPU responding (as in it starts fanning), but nothing visually happens. Nothing is ever started. -- 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/4f15ee67-f291-41e4-b9bf-1b24df5fa915%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: Kernel Panic on a Lenovo Yoga 300 11-iby on attempt at install
Den torsdag den 25. januar 2018 kl. 14.40.14 UTC+1 skrev WolfSkin: > On Thursday, 25 January 2018 13:36:18 UTC, WolfSkin wrote: > > Basically my issue is that I am getting a kernel panic when I try > > installing qubes-os on my laptop both in UEFI and legacy mode. > > The kernel panic can be seen here: https://imagebin.ca/v/3pPwokGAMAVB and I > > sadly can't provide a hastebin dump since I have no way to log the error in > > text form (at least none that I'm aware of). > > > > I have followed the steps in the uefi-troubleshooting docs page, to no avail > > > > Steps to reproduce: > > - Buy this laptop > > - Burn the iso to usb using etcher or rufus after having verified file > > integrity via checksums and signature > > - Boot to the usb in uefi or legacy > > > > What I expect to happen: > > - Normal boot to the installer > > > > What I get instead: > > - Attempts to boot, manages to get to the loading bar on legacy, not even > > close on uefi > > - Then kernel panic (as seen in picture) > > > > Any help with this would be greatly appreciated > > Since I can't edit the above afaik, this is both on R4-rc3 and R3.2 Did you try the steps from this doc page? https://www.qubes-os.org/doc/thinkpad-troubleshooting/#instructions-to-create-usb-installation-medium-for-newer-uefi-only-thinkpads DISCLAIMER: I have a ThinkPad X270, but I installed in legacy mode, so I haven't tried this myself.. Perhaps someone with more knowledge can assist, if this fails :) -- 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/9df52da3-ce82-4036-92a1-a23a0f40bc17%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] i3 under Qubes 4 RC3
Hey all, I installed i3 when first set up my machine, but I can't seem to get it working.. Has anyone else experienced issues with i3? In my case, no applets are shown in the bar and I cannot start any programs from VM's (any VM). If I run qvm-ls, it shows that VM's are running, and if I try to do somethings like qvm-run firefox, my CPU responds. Just a peculiar issue, but makes i3 unusable for me nonetheless.. Any feedback appreciated :) Cheers! -- 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/8a0771c6-0756-41d0-b7a7-f46cbf94b45c%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: [qubes-devel] Qubes Controller as the new Qubes-Manager
Den lørdag den 6. januar 2018 kl. 12.27.18 UTC+1 skrev Tom Zander: > On Saturday, 6 January 2018 00:11:43 GMT Franz wrote: > > I would add some way to make some order in the > > applVM list, so that a standard view may show only the most commonly used > > VMs, while rarely used VMs are hidden and shown only clicking a button. To > > do that, there should be a flag to differentiate the visibility of VMs. > > I made a start with this based on my own usage; See the attached > screenshots. > Going from screenshot1 (showing all my qubes) to 5 by removing ones based > on; > * being templates for disposable VMs. (you likely never want to start them > after initial configuration). > * being a "network" VM. > * Being a template. > * Being halted. > > Naturally you can combine those settings in any way you want to show the > subsection of qubes you use. > I expect that I''l end up using the settings as "snapshot4" shows it most of > the time. > > > This may be helpful also in a corporate environment when an administrator > > can decide which VMs should be shown and which should be hidden. > > This is a great idea, I recall that root added tags in 4.0. I have not tried > them yet, but it sounds like a good fit. > > Thanks for the ideas! > > -- > Tom Zander > Blog: https://zander.github.io > Vlog: https://vimeo.com/channels/tomscryptochannel This is amazing though, good job Tom! -- 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/3945ab58-c37a-47ec-afb5-066137bccca6%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] No network (HELP)
Den fredag den 19. januar 2018 kl. 16.39.31 UTC+1 skrev Marek Marczykowski-Górecki: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA256 > > On Fri, Jan 19, 2018 at 06:53:55AM -0800, aaq via qubes-users wrote: > > Den fredag den 19. januar 2018 kl. 15.48.08 UTC+1 skrev a...@it-minds.dk: > > > Which setting exactly disables dynamic memory allocation, because I can't > > > seem to figure it out. If I set maxmem to 0, will it disable it? > > > > > > The GUI is broken. It comes up with an error if I try to start it, no > > > matter how I try to start it. It complains about a bug, but that isn't > > > really important right now. > > It's a bit obscure, see qvm-service. "meminfo-writer" service is > responsible for memory balancing. But it should be already in "off" > state for sys-net. > > > I set the maxmem to 1 (cannot set it to 0) and initial mem to 800. > > This is maximum memory size in MB. Setting it to 1 doesn't sounds like a > good idea, but... for VMs with PCI devices it is ignored and "memory" > property is used instead (because of Xen limitation, namely > populate-on-demand being incompatible with PCI-passthrough). > > 400MB should be enough for sys-net, in some cases even lower number > should suffice. > > > sys-net starts now. > > > > I am updating my system now, hopefully this will disappear on its own. > > There were a bunch of fixes yesterday (late) evening, including one for > qmemman, and GUI stuff. Make sure you have: > > qubes-core-dom0 4.0.18 > qubes-core-admin-client 4.0.13 > qubes-manager 4.0.11 > qubes-dbus 1.0.4 > > Specifically qmemman was broken in qubes-core-dom0 in 4.0.16 and 4.0.17. > > - -- > Best Regards, > Marek Marczykowski-Górecki > Invisible Things Lab > A: Because it messes up the order in which people normally read text. > Q: Why is top-posting such a bad thing? > -BEGIN PGP SIGNATURE- > > iQEzBAEBCAAdFiEEhrpukzGPukRmQqkK24/THMrX1ywFAlpiEQ4ACgkQ24/THMrX > 1ywPywf/Tl8SsGq0NQ5zQC2uiMIWrkEipbRj0hMkeeqIIQQpgzn101bDlLgoud+w > JzbBUfRqA1tO2KUWhOG0XRcuUiRQszOhR95p13hMsoEm4Nnxu0chFietPe7aOQZx > sMQqr3BjHkJxtYh780F6reke9Ec0fvkxANnKC4J53YocEQSIGtqX7GSUuxdEYM0K > T02DpNJJseocFO6s2G8aTqQpTiorl+mWVvdL8PjzlJ7XOduLVtHna3sZL5LrbP18 > 3SsTWZQ5bhRfk/3Elt0t26UYe+Aeyeyxric/HCbe7nmWqxrNqqnZkjpNXkFZi+9F > oDHvHUm5N834oxlidhG2gGwr0u2bCw== > =w6SK > -END PGP SIGNATURE- 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/82a29f20-68c9-4ee8-b942-f0c1ecc1fd0f%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] No network (HELP)
Den fredag den 19. januar 2018 kl. 15.48.08 UTC+1 skrev a...@it-minds.dk: > Den fredag den 19. januar 2018 kl. 15.44.35 UTC+1 skrev awokd: > > On Fri, January 19, 2018 2:33 pm, aaq via qubes-users wrote: > > > Den fredag den 19. januar 2018 kl. 15.28.27 UTC+1 skrev awokd: > > > > > >> On Fri, January 19, 2018 1:48 pm, aaq via qubes-users wrote: > > >> > > >>> Den fredag den 19. januar 2018 kl. 14.44.26 UTC+1 skrev > > >>> a...@it-minds.dk: > > >>> > > >>> > > >>>> Den fredag den 19. januar 2018 kl. 14.08.21 UTC+1 skrev Tom Zander: > > >>>> > > >>>> > > >>>>> On Friday, 19 January 2018 11:48:56 CET aaq via qubes-users > > >>>>> wrote: > > >>>>> > > >>>>> > > >> > > >>>>> Try turning off memory-management and give the sys-net an initial > > >>>>> amount of something like 800MB. > > >> > > >> Go into sys-net's VM Settings, Advanced tab. Uncheck "include in memory > > >> balancing" and increase initial memory to 800. > > >> > > >> See if there are any other errors in dom0 with "sudo journalctl -b" > > >> when you start the VM. > > > > > > Can I disable it through qvm-prefs? Because my qubes manager (the GUI is > > > back again now) is broken.. > > > > Yes, type qvm-prefs sys-net to see a list of settings. qubes-vm-settings > > sys-net should also give you the gui. > > Sorry. > > Which setting exactly disables dynamic memory allocation, because I can't > seem to figure it out. If I set maxmem to 0, will it disable it? > > The GUI is broken. It comes up with an error if I try to start it, no matter > how I try to start it. It complains about a bug, but that isn't really > important right now. Okay! I set the maxmem to 1 (cannot set it to 0) and initial mem to 800. sys-net starts now. I am updating my system now, hopefully this will disappear on its own. Any deeper insight as to the 'why'? I am kind of confused.. Without your guys' suggestions I would have been lost.. Thanks a bunch! -- 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/59912f3c-476f-494d-9bc8-5a77a8f379f2%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] No network (HELP)
Den fredag den 19. januar 2018 kl. 15.44.35 UTC+1 skrev awokd: > On Fri, January 19, 2018 2:33 pm, aaq via qubes-users wrote: > > Den fredag den 19. januar 2018 kl. 15.28.27 UTC+1 skrev awokd: > > > >> On Fri, January 19, 2018 1:48 pm, aaq via qubes-users wrote: > >> > >>> Den fredag den 19. januar 2018 kl. 14.44.26 UTC+1 skrev > >>> a...@it-minds.dk: > >>> > >>> > >>>> Den fredag den 19. januar 2018 kl. 14.08.21 UTC+1 skrev Tom Zander: > >>>> > >>>> > >>>>> On Friday, 19 January 2018 11:48:56 CET aaq via qubes-users > >>>>> wrote: > >>>>> > >>>>> > >> > >>>>> Try turning off memory-management and give the sys-net an initial > >>>>> amount of something like 800MB. > >> > >> Go into sys-net's VM Settings, Advanced tab. Uncheck "include in memory > >> balancing" and increase initial memory to 800. > >> > >> See if there are any other errors in dom0 with "sudo journalctl -b" > >> when you start the VM. > > > > Can I disable it through qvm-prefs? Because my qubes manager (the GUI is > > back again now) is broken.. > > Yes, type qvm-prefs sys-net to see a list of settings. qubes-vm-settings > sys-net should also give you the gui. Sorry. Which setting exactly disables dynamic memory allocation, because I can't seem to figure it out. If I set maxmem to 0, will it disable it? The GUI is broken. It comes up with an error if I try to start it, no matter how I try to start it. It complains about a bug, but that isn't really important right now. -- 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/71be7916-6e82-4265-8844-ca25d5c1106b%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] No network (HELP)
Den fredag den 19. januar 2018 kl. 15.28.27 UTC+1 skrev awokd: > On Fri, January 19, 2018 1:48 pm, aaq via qubes-users wrote: > > Den fredag den 19. januar 2018 kl. 14.44.26 UTC+1 skrev a...@it-minds.dk: > > > >> Den fredag den 19. januar 2018 kl. 14.08.21 UTC+1 skrev Tom Zander: > >> > >>> On Friday, 19 January 2018 11:48:56 CET aaq via qubes-users wrote: > >>> > > >>> Try turning off memory-management and give the sys-net an initial > >>> amount of something like 800MB. > > Go into sys-net's VM Settings, Advanced tab. Uncheck "include in memory > balancing" and increase initial memory to 800. > > See if there are any other errors in dom0 with "sudo journalctl -b" when > you start the VM. Can I disable it through qvm-prefs? Because my qubes manager (the GUI is back again now) is broken.. -- 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/3b0badb7-cb9e-4e59-b7d7-4f9fa897e5da%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] No network (HELP)
Den fredag den 19. januar 2018 kl. 14.44.26 UTC+1 skrev a...@it-minds.dk: > Den fredag den 19. januar 2018 kl. 14.08.21 UTC+1 skrev Tom Zander: > > On Friday, 19 January 2018 11:48:56 CET aaq via qubes-users wrote: > > > What can I do > > > > Could this have something to do with the broken qmemman? > > > > Try turning off memory-management and give the sys-net an initial amount of > > something like 800MB. > > > > also check if xentop has anything weird in the first line with memory usage. > > > > Good luck! > > > Can you give me specific instructions to where I can do these things :S > > Sorry! > > I know there is something in the grub config for dom0 memory management, is > it that? > > Where do I find xentop? > > I can see in /var/log/xen/console/hypervisor.log that it complains about > "initial memory low", but I dunno if that's new.. > > I tried awokds recommendations: > switching template to debian yields same message about memory being too low. > virt_mode already is hvm. > > Thanks for your time and help. Sorry, I didn't release xentop was a tool like top/htop... My laptop has 8gb of RAM, Qubes has reserved 4gb to dom0 through grub config. Xentop says that approx. 3.8gb is free. So I really don't think the issues lies there. -- 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/898e2d6f-cba3-4142-bbae-152a13ff2bde%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] No network (HELP)
Den fredag den 19. januar 2018 kl. 14.08.21 UTC+1 skrev Tom Zander: > On Friday, 19 January 2018 11:48:56 CET aaq via qubes-users wrote: > > What can I do > > Could this have something to do with the broken qmemman? > > Try turning off memory-management and give the sys-net an initial amount of > something like 800MB. > > also check if xentop has anything weird in the first line with memory usage. > > Good luck! Can you give me specific instructions to where I can do these things :S Sorry! I know there is something in the grub config for dom0 memory management, is it that? Where do I find xentop? I can see in /var/log/xen/console/hypervisor.log that it complains about "initial memory low", but I dunno if that's new.. I tried awokds recommendations: switching template to debian yields same message about memory being too low. virt_mode already is hvm. Thanks for your time and help. -- 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/1fd6f7cc-3941-458d-aa71-ef7f275932e1%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] No network (HELP)
Qubes 4 RC3 So, I updated using current testing yesterday, and there was an update to qubes core dom0 and other changes.. Network worked fine before I shutdown my machine, but now when I try to start sys-net I get an error saying "Not enough memory to start domain 'sys-net'" I have tried rebooting, and I have tried upscaling and downscaling the initial memory to sys-net with qvm-prefs sys-net memory XX I can start my templateVM's with no issue (eg fedora-26 which is my template for sys-net/sys-firewall, and I have tried starting my debian 9 template). What can I do :S Needless to say it is pretty fatal for me that I have no network. Thanks in advance. -- 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/34fa87a3-eedc-4c6a-982e-16c61257e769%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: Multiple usability issues Qubes 4RC3
Den fredag den 12. januar 2018 kl. 12.38.20 UTC+1 skrev awokd: > On Fri, January 12, 2018 10:12 am, aaq via qubes-users wrote: > > > 6) Resizing a urxvt window in my debian unstable to a certain dimension > > (or fullscreen hotkey) crashes the terminal. If I have another window > > running the VM, and that window already 'broke' the dimensions in > > question, then urxvt has no issues taking on any dimensions. If urxvt is > > the only window running in the appvm, it will however keep crashing when > > it reaches a specific size. > > That sounds like this issue: > https://github.com/QubesOS/qubes-issues/issues/2617. Try starting from a > fresh Qubes Stretch template and upgrading it to unstable. If that's what > you did, it might be a regression. Can anything be done to fix this? I can't seem to find a solution in that issue, other than core components being updated. It's fine with me if there aren't any workarounds btw. Just wondering :) -- 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/2d2c8071-359d-44fa-af9f-8004a52a62fb%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: Multiple usability issues Qubes 4RC3
Den fredag den 12. januar 2018 kl. 10.45.02 UTC+1 skrev a...@it-minds.dk: > Den mandag den 8. januar 2018 kl. 14.29.06 UTC+1 skrev Ahmed Al Aqtash: > > Hello all! > > > > > > I apologise for the vague subject, but I have been trying all kinds of > > things, and I simply can't understand half of the issues, and the other > > half I can't seem to find a solution to. > > > > > > First of all I have all the respect in the world for the entire Qubes team, > > and I sincerely believe that you are making the world a better place. > > > > > > The machine: ThinkPad X270 (full specs: > > https://www.uk.insight.com/en-gb/productinfo/portatili-e-notebook/0007017591). > > It has 8 GB RAM. > > > > > > So.. to the issues.. > > 1) A more general gripe with not having enough documentation to actually > > get through a setup process. I used Qubes 3.2 before, and I simply went > > about Qubes 4 the same way. I know that there have been multiple changes, > > and I honestly believe the changes are for the better. > > > > > > But issues like moving a templates home directory to /etc/skel (meaning > > that appvm's inherit /etc/skel as home dir from the template) left me > > baffled with my first install.. I setup my template exactly as I wanted, > > created an appvm, and nothing was initialised. I had no idea what was going > > on, and the only way I could get some information was through a GitHub > > issue. Even after moving everything over to /etc/skel, I still have > > issues.. not everything is being carried over, not everything is being read > > correctly, and /etc/skel is not being synchronised either. If I add > > something new to /etc/skel AFTER creating a appvm, the appvm's homedir > > won't be updated. > > > > > > I like the idea with moving all the GUI functionality to the shell. I > > prefer using the shell anyway. But for instance, in 3.2, you could allow > > access to through the firewall for a templatevm. Now it has to be done > > through qvm-prefs. This is not documented anywhere, and this was also an > > infuriating issue for me. > > > > > > 2) I have reinstalled qubes multiple times over the weekend (friday through > > sunday) to get my install at a state that I am actually satisfied with. > > > > > > Most griping issues: sys-net and sys-firewall do not start on boot. > > Journalctl claims that there isn't enough memory to start sys-net on boot > > (I don't have anything more descriptive for sys-firewall). > > I can easily start them after boot and login. If I need more memory, then I > > will happily upgrade. I intended to do so anyway, but I cannot understand > > why it worked fine in 3.2 with 8 GB RAM. > > > > > > 3) The issue mentioned under documentation with setting up a template > > exactly the way I want it. > > To understand the issue in depth, I think it's in place to describe my > > setup: > > Having 2 base templates (based on the debian 9 template): > > > > > > * One I call 'trusted' which is based on debian sid (unstable) that I > > install everything I use for daily usage (firefox, libreoffice, mpv, emacs, > > other open source tools). Primarily AppVM's will be based out of this > > template. > > > > > > * One I call 'untrusted' that is going to be a clone of 'trusted', and that > > I install proprietary software in, that I also use on a daily basis (e.g. > > spotify). Also AppVM's out of this, but probably only 1 to start with. > > > > > > * I will probably create a standalone VM based off of 'trusted' that I use > > for development. So I will install stuff like docker, golang, and all other > > stuff I would otherwise use for developing. > > > > > > I have not been able to create my 'trusted' template in a proper manner, > > since I can't get /etc/skel to work properly. > > > > > > NOTE: I use zsh with oh my zsh and spacemacs. Both of which are git repos > > that are cloned to the homedir of the user (meaning they are git repos > > cloned to /etc/skel) > > If this is improper usage, then please guide me to how I should go about > > doing this instead, as I have no idea what the smartest solution would > > otherwise be. > > > > > > Sorry for the long email, and thanks in advance for clarifying answers. > > > > > > Best regards and all the best. > > UPDATE: > > So, I decided to go on with an install and with the knowledge of my previous > misinstalls and guidance from here this is the result: > > 1) I decided to go on with the install and scheme that I already wrote about. > I looked into bind-dirs, and it is definitely something I am going to use at > some point, but the effort right now on a 'per-application basis' is simply > too much (I just need a running system). > > 2) I still have an issue with sys-net/sys-firewall not being started on boot, > but this problem isn't really a dealbreaker for me. It's just an annoyance. > > 3) Sound doesn't seem to be working in debian (unstable). None of the fixes > seem
[qubes-users] Re: Multiple usability issues Qubes 4RC3
Den mandag den 8. januar 2018 kl. 14.29.06 UTC+1 skrev Ahmed Al Aqtash: > Hello all! > > > I apologise for the vague subject, but I have been trying all kinds of > things, and I simply can't understand half of the issues, and the other half > I can't seem to find a solution to. > > > First of all I have all the respect in the world for the entire Qubes team, > and I sincerely believe that you are making the world a better place. > > > The machine: ThinkPad X270 (full specs: > https://www.uk.insight.com/en-gb/productinfo/portatili-e-notebook/0007017591). > It has 8 GB RAM. > > > So.. to the issues.. > 1) A more general gripe with not having enough documentation to actually get > through a setup process. I used Qubes 3.2 before, and I simply went about > Qubes 4 the same way. I know that there have been multiple changes, and I > honestly believe the changes are for the better. > > > But issues like moving a templates home directory to /etc/skel (meaning that > appvm's inherit /etc/skel as home dir from the template) left me baffled with > my first install.. I setup my template exactly as I wanted, created an appvm, > and nothing was initialised. I had no idea what was going on, and the only > way I could get some information was through a GitHub issue. Even after > moving everything over to /etc/skel, I still have issues.. not everything is > being carried over, not everything is being read correctly, and /etc/skel is > not being synchronised either. If I add something new to /etc/skel AFTER > creating a appvm, the appvm's homedir won't be updated. > > > I like the idea with moving all the GUI functionality to the shell. I prefer > using the shell anyway. But for instance, in 3.2, you could allow access to > through the firewall for a templatevm. Now it has to be done through > qvm-prefs. This is not documented anywhere, and this was also an infuriating > issue for me. > > > 2) I have reinstalled qubes multiple times over the weekend (friday through > sunday) to get my install at a state that I am actually satisfied with. > > > Most griping issues: sys-net and sys-firewall do not start on boot. > Journalctl claims that there isn't enough memory to start sys-net on boot (I > don't have anything more descriptive for sys-firewall). > I can easily start them after boot and login. If I need more memory, then I > will happily upgrade. I intended to do so anyway, but I cannot understand why > it worked fine in 3.2 with 8 GB RAM. > > > 3) The issue mentioned under documentation with setting up a template exactly > the way I want it. > To understand the issue in depth, I think it's in place to describe my setup: > Having 2 base templates (based on the debian 9 template): > > > * One I call 'trusted' which is based on debian sid (unstable) that I > install everything I use for daily usage (firefox, libreoffice, mpv, emacs, > other open source tools). Primarily AppVM's will be based out of this > template. > > > * One I call 'untrusted' that is going to be a clone of 'trusted', and that I > install proprietary software in, that I also use on a daily basis (e.g. > spotify). Also AppVM's out of this, but probably only 1 to start with. > > > * I will probably create a standalone VM based off of 'trusted' that I use > for development. So I will install stuff like docker, golang, and all other > stuff I would otherwise use for developing. > > > I have not been able to create my 'trusted' template in a proper manner, > since I can't get /etc/skel to work properly. > > > NOTE: I use zsh with oh my zsh and spacemacs. Both of which are git repos > that are cloned to the homedir of the user (meaning they are git repos cloned > to /etc/skel) > If this is improper usage, then please guide me to how I should go about > doing this instead, as I have no idea what the smartest solution would > otherwise be. > > > Sorry for the long email, and thanks in advance for clarifying answers. > > > Best regards and all the best. UPDATE: So, I decided to go on with an install and with the knowledge of my previous misinstalls and guidance from here this is the result: 1) I decided to go on with the install and scheme that I already wrote about. I looked into bind-dirs, and it is definitely something I am going to use at some point, but the effort right now on a 'per-application basis' is simply too much (I just need a running system). 2) I still have an issue with sys-net/sys-firewall not being started on boot, but this problem isn't really a dealbreaker for me. It's just an annoyance. 3) Sound doesn't seem to be working in debian (unstable). None of the fixes seem to work either. This is kind of critical to me.. 4) All around okay for now, but I can definitely tell that I would love some more stability, but that's just a matter of patience :) Thank you for your assistance Tom, much appreciated. I hope this thread can help others. -- You received this
Re: [qubes-users] Change Inter-VM Copy/Paste Shortcut?
Den onsdag den 10. januar 2018 kl. 10.05.32 UTC+1 skrev Rune Philosof: > On Saturday, June 25, 2016 at 7:49:39 PM UTC+2, cubit wrote: > > To use the Windows Key, it is `Mod4` > > > > > > "Mod4-c" > > "Mod4-v" > > How did you figure that out? > I haven't been able to find documentation with a list available modifier > names. > I tried using the names from `xev`'s output with no luck. I have no idea what xev gives, but mod4 is pretty much the 'super' key (or Windows key). 'Mod' is usually the Alt (left Alt) key. I know this because I used tiling window managers a lot, and from there I knew that Mod4 = Windows key. I don't know what the deeper meaning is, where it's bound, or why it has that name :) -- 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/97f69a2b-c05c-459d-891a-3101d69d50b4%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Multiple usability issues Qubes 4RC3
Den mandag den 8. januar 2018 kl. 14.52.43 UTC+1 skrev Tom Zander: > On Monday, 8 January 2018 13:29:02 GMT 'Ahmed Al Aqtash' via qubes-users > wrote: > > * One I call 'trusted' which is based on debian sid (unstable) that I > > install everything I use for daily usage (firefox, libreoffice, mpv, > > emacs, other open source tools). Primarily AppVM's will be based out of > > this template. > > > > * One I call 'untrusted' that is going to be a clone of 'trusted', and > > that I install proprietary software in, that I also use on a daily basis > > (e.g. spotify). Also AppVM's out of this, but probably only 1 to start > > with. > > An alternative solution is to make your "untrusted" VM an AppVM and you > install the software in there using bind-dirs. > Then you *only* use that VM for running that software and you likely store > no personal data there (other than maybe your spotify cridentials). > > Additional bonus would be to open any webpages in disposable VMs, should you > click on a link in any of those apps. Okay, so I found the documentation for bind-dirs (https://www.qubes-os.org/doc/bind-dirs/), but was still wondering if you meant binding the AppVMs /usr/bin and /usr/local/bin, or was thinking of something else? I would assume I need to bind all dirs that a given application is going to write to (such as potentionally /usr/share, /var/lib, etc). Any thoughts? -- 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/06ab2226-4ec2-4715-a8b5-4b60b737c247%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: Multiple usability issues Qubes 4RC3
Den mandag den 8. januar 2018 kl. 14.29.06 UTC+1 skrev Ahmed Al Aqtash: > Hello all! > > > I apologise for the vague subject, but I have been trying all kinds of > things, and I simply can't understand half of the issues, and the other half > I can't seem to find a solution to. > > > First of all I have all the respect in the world for the entire Qubes team, > and I sincerely believe that you are making the world a better place. > > > The machine: ThinkPad X270 (full specs: > https://www.uk.insight.com/en-gb/productinfo/portatili-e-notebook/0007017591). > It has 8 GB RAM. > > > So.. to the issues.. > 1) A more general gripe with not having enough documentation to actually get > through a setup process. I used Qubes 3.2 before, and I simply went about > Qubes 4 the same way. I know that there have been multiple changes, and I > honestly believe the changes are for the better. > > > But issues like moving a templates home directory to /etc/skel (meaning that > appvm's inherit /etc/skel as home dir from the template) left me baffled with > my first install.. I setup my template exactly as I wanted, created an appvm, > and nothing was initialised. I had no idea what was going on, and the only > way I could get some information was through a GitHub issue. Even after > moving everything over to /etc/skel, I still have issues.. not everything is > being carried over, not everything is being read correctly, and /etc/skel is > not being synchronised either. If I add something new to /etc/skel AFTER > creating a appvm, the appvm's homedir won't be updated. > > > I like the idea with moving all the GUI functionality to the shell. I prefer > using the shell anyway. But for instance, in 3.2, you could allow access to > through the firewall for a templatevm. Now it has to be done through > qvm-prefs. This is not documented anywhere, and this was also an infuriating > issue for me. > > > 2) I have reinstalled qubes multiple times over the weekend (friday through > sunday) to get my install at a state that I am actually satisfied with. > > > Most griping issues: sys-net and sys-firewall do not start on boot. > Journalctl claims that there isn't enough memory to start sys-net on boot (I > don't have anything more descriptive for sys-firewall). > I can easily start them after boot and login. If I need more memory, then I > will happily upgrade. I intended to do so anyway, but I cannot understand why > it worked fine in 3.2 with 8 GB RAM. > > > 3) The issue mentioned under documentation with setting up a template exactly > the way I want it. > To understand the issue in depth, I think it's in place to describe my setup: > Having 2 base templates (based on the debian 9 template): > > > * One I call 'trusted' which is based on debian sid (unstable) that I > install everything I use for daily usage (firefox, libreoffice, mpv, emacs, > other open source tools). Primarily AppVM's will be based out of this > template. > > > * One I call 'untrusted' that is going to be a clone of 'trusted', and that I > install proprietary software in, that I also use on a daily basis (e.g. > spotify). Also AppVM's out of this, but probably only 1 to start with. > > > * I will probably create a standalone VM based off of 'trusted' that I use > for development. So I will install stuff like docker, golang, and all other > stuff I would otherwise use for developing. > > > I have not been able to create my 'trusted' template in a proper manner, > since I can't get /etc/skel to work properly. > > > NOTE: I use zsh with oh my zsh and spacemacs. Both of which are git repos > that are cloned to the homedir of the user (meaning they are git repos cloned > to /etc/skel) > If this is improper usage, then please guide me to how I should go about > doing this instead, as I have no idea what the smartest solution would > otherwise be. > > > Sorry for the long email, and thanks in advance for clarifying answers. > > > Best regards and all the best. Another issue actually: What is the best/recommended way of updating software in TemplateVMs? Firing up a shell in the TemplateVM and running a standard 'sudo dnf update'/'sudo apt-get upgrade', or should we throw flags at it? In 3.2 the GUI would happily say 'you have updates', but now (with my very limited knowledge) we have to check this manually? Cheers -- 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/706226d9-5e3b-4145-a042-3866f7aa192a%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Multiple usability issues Qubes 4RC3
> > * One I call 'trusted' which is based on debian sid (unstable) that I > > install everything I use for daily usage (firefox, libreoffice, mpv, > > emacs, other open source tools). Primarily AppVM's will be based out of > > this template. > > > > * One I call 'untrusted' that is going to be a clone of 'trusted', and > > that I install proprietary software in, that I also use on a daily basis > > (e.g. spotify). Also AppVM's out of this, but probably only 1 to start > > with. > > An alternative solution is to make your "untrusted" VM an AppVM and you > install the software in there using bind-dirs. > Then you *only* use that VM for running that software and you likely store > no personal data there (other than maybe your spotify cridentials). > > Additional bonus would be to open any webpages in disposable VMs, should you > click on a link in any of those apps. This approach is actually quite nice. I have never used bind-dirs though. How would I go about this? Symlink from /usr/bin to the homedir of the VM, or how? I actually already open all links in disposable VMs, unless of course it is something that I use/trust. So that part of the equation is solved :) > > * I will probably create a standalone VM based off of 'trusted' that I use > > for development. So I will install stuff like docker, golang, and all > > other > > stuff I would otherwise use for developing. > > I may be wrong, but all those development tools are open source and likely > shipped by your distro. In which case I wonder what the benefit is to putting > them into its own VM? I may use libs that I haven't neccessarily looked through, or have no idea where originate from. Also, this VM will need to communicate more extensively with the Internet, as I make web utils or other stuff. I would prefer having this VM isolated at any rate :) > In short, maybe the simplest way is to create; > > * TemplateVM: debian9 > * Work AppVM based on debian9 > * Untrusted AppVM based on debian9, adds untrusted apps using binds > * any other AppVMs you need... All based on the same debian9 template. > > > NOTE: I use zsh with oh my zsh and spacemacs. Both of which are git repos > > that are cloned to the homedir of the user (meaning they are git repos > > cloned to /etc/skel) > > Using /etc/skel just causes the data to be copied to the appvm homedir on > first start. > You end up duplicating the data anyway, maybe you can use a different way to > copy everthing between VM homedirs. > Notice that you can just do a qvm-copy [dir] which copies recursively. But it's fine by me if it only happens once. That means I just need to setup the template exactly the way I want, before I create AppVMs. I'd rather clone the repos and copy my settings files, .ssh, and other config/setup stuff in my template once, than doing it for all AppVMs. Thanks again for your help Tom :) I still need assistance with the initial start up of sys-net and sys-firewall though :( -- 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/5ecf4340-34ea-4a2c-847b-2cfb2aa59893%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] How do I install and configure a template vm in Qubes 4?
> The same functionality is present in Qubes4, just not via a GUI. > > open a terminal in dom0 (adminvm) and type; > > qvm-prefs -s YOURVMNAME netvm sys-firewall > > When you are done downloading consider unsetting the netvm with; > qvm-prefs -s YOURVMNAME netvm "" I thought so, I just can't seem to find any information anywhere. I might just be stupid, or not looking closely enough. I can see I need to read the documentation more carefully too, and look into all the new tools. Thanks a bunch! > > I'll add the warning that you should be careful what you do in a TemplateVM, > anything you run or download has sudo and can install or change data which > then will cause all your VMs based on this template to be contaminated. > Be safe. Yeah, I know. I am only installing open source stuff, and things I actually trust. It is primarily for my template for private usage. I wouldn't install weird stuff in there :) Again thanks! -- 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/715c7e94-5f1e-4357-9b49-7dae276cc98c%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
