Re: [qubes-users] Thank You & How to "Give Back"?
Hey John, On 1/16/19 8:20 PM, John Goold wrote: > I want to say thank you to those members of Qubes Users who have had the > patience to answer my questions and solve my problems getting Qubes up and > running. I have been particularly pleased that this is a forum where there > are few, if any, unhelpful responses to questions and few questions/requests > for help where the asker has not tried to find the answer in this forum or in > the documentation. Thank you. As a long time user of Qubes OS I don't see how I could do without it so I'm happy to help the community here. Kind of "giving back" as you say. I'm sure it applies to the other users who helped you as well. > While I have a computer background, my entire career was spend in the > software/research environment, I do not have a background in PC/Linux > internals (though decades ago I did acquire some Unix sys-admin knowledge). > That means I came to Qubes without the the in-depth security knowledge that > the more knowledgeable of you have — my knowledge is more superficial. > > Having provided that background, I was trying to think of a way of "giving > back" to this community. > > Would a "Setting up a Semi-Secure Personal Computing Environment Using Qubes" > document be a useful addition (albeit, with a more succinct title!)? > > It would be aimed at computer users who want a more secure environment, but > are willing to live with some security exposures (ones that hopefully have an > exceedingly low probability of being exploited against an "average Joe") — > for example, using a USB mouse and keyboard. Clearly one needs to have some > degree of computer literacy to tackle switching to Qubes, but I think a > step-by-step migration guide might be useful and fewer people might give up. > > In it, I could briefly describe the "Hardware Issues" which are already well > documented (hence "briefly" as they applied to me) and then get into the > issues of choosing which qubes to set up, the issues of dealing with a > desktop computer that only has USB mouse/keyboard capability, various > user-interface issues and, perhaps more importantly, migrating data from > another OS (in my case Linux Mint) to the Qubes environment. In my opinion such document may be helpful as a blog post - but the problem would be visibility (only through search engines). Maybe a better way would be to improve the official qubes docs where you found things to be lacking details/clarity [1]. Some people find it easy to deal with the official docs, others don't. In the latter case you could float ideas/pull requests in the unofficial "qubes community" project [2] and folks there (including myself) would help you format them for submission to the official docs. Writing docs can be time consuming though, so in any case spending a bit of time helping other people on the ML is already a nice way of "giving back" ! [1] https://www.qubes-os.org/doc/doc-guidelines/#how-to-contribute [2] https://qubes-community.github.io/ -- 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/2b714c9c-93ac-f025-96d1-3210c85ebc02%40maa.bz. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: Intel X540-AT2 network card worked in Qubes 3.2, fails in 4.0.1?
> Having just installed Qubes 4.0.1 I am not able to get my 10Gb Intel X540-AT2 > network card to work. It worked out of the box in Qubes 3.2. > > This is what I get in the net-vm: > > $ sudo dmesg |grep ixgbe > [2.737931] ixgbe: Intel(R) 10 Gigabit PCI Express Network Driver - > version 5.1.0-k > [2.737971] ixgbe: Copyright (c) 1999-2016 Intel Corporation. > [3.045650] ixgbe :00:06.0: Failed to allocate MSI-X interrupts. Err: > -22 > [3.045658] ixgbe :00:06.0: Disabling SR-IOV support > [3.045665] ixgbe :00:06.0: Disabling RSS support > [3.049104] ixgbe :00:06.0: Multiqueue Disabled: Rx Queue count = 1, > Tx Queue count = 1 XDP Queue count = 0 > [3.181722] ixgbe :00:06.0: MAC: 3, PHY: 0, PBA No: G35632-015 > [3.181730] ixgbe :00:06.0: a0:36:9f:83:8c:e0 > [3.333064] ixgbe :00:06.0: Intel(R) 10 Gigabit Network Connection > [3.347927] ixgbe :00:06.0 ens6f0: renamed from eth0 > [3.878232] ixgbe :00:06.0: registered PHC device on ens6f0 > > The "Failed to allocate MSI-X interrupts" doesn't look very good? > > The problem is that the network link never becomes ready: > > $ sudo dmesg |grep link > [3.864405] IPv6: ADDRCONF(NETDEV_UP): ens6f0: link is not ready > [4.013735] IPv6: ADDRCONF(NETDEV_UP): ens6f0: link is not ready > > > Is this a known problem? What should I try next? While waiting for a solution to this problem, can anybody recommend a 10Gb network card that *does* work with Qubes 4.x? -- 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/223e-9f53-4904-9bb3-175023024f52%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Macbook Pro (Retina, 13-inch, Early 2015):Qubes R3.2.1 no network device available
The following problem happened only on Qubes R3.2.1 Following the steps on https://www.qubes-os.org/doc/macbook-troubleshooting/#7-fix-system-freezes-due-to-broadcom-bcm43602 sudo su - xl pci-assignable-list echo 03:00.0 > /sys/bus/pci/drivers/pciback/permissive qvm-start sys-net xl pci-attach sys-net 03:00.0 There should be wifi showing so that I can connect but `Device not managed` showed under Ethernet Network in the networkmanager applet -- 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/411b8d30-6181-4d2b-a347-5501a3a03223%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Macbook Pro (Retina, 13-inch, Early 2015):Qubes R3.2.1 no network device available
Qubes OS version: Qubes 3.2.1 Affected component(s): Qubes R3.2.1 System Network manager Steps to reproduce the behavior: Following the steps on https://www.qubes-os.org/doc/macbook-troubleshooting/#7-fix-system-freezes-due-to-broadcom-bcm43602;>this sudo su - xl pci-assignable-list echo 03:00.0 /sys/bus/pci/drivers/pciback/permissive qvm-start sys-net xl pci-attach sys-net 03:00.0 Expected behavior: There should be wifi showing so that I can connect Actual behavior: Device not managed showed under Ethernet Network in the networkmanager applet -- 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/dbae4e61-586a-4230-8028-e94e5b64da9a%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Macbook Pro (Retina, 13-inch, Early 2015):Qubes R3.2.1 no network device available
### Qubes OS version: Qubes 3.2.1 ### Affected component(s): Qubes R3.2.1 System Network manager ### Steps to reproduce the behavior: Following the steps on [this](https://www.qubes-os.org/doc/macbook-troubleshooting/#7-fix-system-freezes-due-to-broadcom-bcm43602) ``` sudo su - xl pci-assignable-list echo 03:00.0 > /sys/bus/pci/drivers/pciback/permissive qvm-start sys-net xl pci-attach sys-net 03:00.0 ``` ### Expected behavior: There should be wifi showing so that I can connect ### Actual behavior: `Device not managed` showed under Ethernet Network in the networkmanager applet -- 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/847edb28-d92a-4a10-bc64-35dae6a529fa%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Renaming .desktop file side-effect
On Wed, Jan 16, 2019 at 01:19:54PM -0800, John Goold wrote: > I encountered an "interesting" phenomenon which could be a defect (bug) or > expected behaviour (an odd "feature"). If a defect, it could be in the file > manager under Debian (Nautilus?). > > If I attempt to rename a file in ~/local/share/applications/ when I save the > change, ".desktop" is appended to the file name. This occurs even if the name > entered in the rename dialog already has a .desktop extension. > > An example: I copied dropbox.desktop from /usr/share/applications to > ~/local/share/applications (to use as a template). Renaming it by just > changing "dropbox" to "vuescan" resulted in vuescan.desktop.desktop. > > It took me a few minutes to realize what was happening :-( The easy > workaround was to remove the .desktop file extension when renaming as it > would automatically get appended. > > Surely this is unexpected behaviour? Does anyone know if this is a "feature" > and will it pop-up when attempting to rename files in other directories? > It is a "feature" of Gnome Files, not specific to Debian, and is expected behaviour. (bizarre but expected in the mysterious world of Gnome.) I think that it applies only to files in the applications directories and was presumably introduced to ensure that launchers would not be 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/20190117015310.kkkulazhrrqiy5nj%40thirdeyesecurity.org. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Renaming .desktop file side-effect
I encountered an "interesting" phenomenon which could be a defect (bug) or expected behaviour (an odd "feature"). If a defect, it could be in the file manager under Debian (Nautilus?). If I attempt to rename a file in ~/local/share/applications/ when I save the change, ".desktop" is appended to the file name. This occurs even if the name entered in the rename dialog already has a .desktop extension. An example: I copied dropbox.desktop from /usr/share/applications to ~/local/share/applications (to use as a template). Renaming it by just changing "dropbox" to "vuescan" resulted in vuescan.desktop.desktop. It took me a few minutes to realize what was happening :-( The easy workaround was to remove the .desktop file extension when renaming as it would automatically get appended. Surely this is unexpected behaviour? Does anyone know if this is a "feature" and will it pop-up when attempting to rename files in other directories? -- 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/17365c91-8367-4fa5-97e1-9337fda5314c%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Thank You & How to "Give Back"?
I want to say thank you to those members of Qubes Users who have had the patience to answer my questions and solve my problems getting Qubes up and running. I have been particularly pleased that this is a forum where there are few, if any, unhelpful responses to questions and few questions/requests for help where the asker has not tried to find the answer in this forum or in the documentation. While I have a computer background, my entire career was spend in the software/research environment, I do not have a background in PC/Linux internals (though decades ago I did acquire some Unix sys-admin knowledge). That means I came to Qubes without the the in-depth security knowledge that the more knowledgeable of you have — my knowledge is more superficial. Having provided that background, I was trying to think of a way of "giving back" to this community. Would a "Setting up a Semi-Secure Personal Computing Environment Using Qubes" document be a useful addition (albeit, with a more succinct title!)? It would be aimed at computer users who want a more secure environment, but are willing to live with some security exposures (ones that hopefully have an exceedingly low probability of being exploited against an "average Joe") — for example, using a USB mouse and keyboard. Clearly one needs to have some degree of computer literacy to tackle switching to Qubes, but I think a step-by-step migration guide might be useful and fewer people might give up. In it, I could briefly describe the "Hardware Issues" which are already well documented (hence "briefly" as they applied to me) and then get into the issues of choosing which qubes to set up, the issues of dealing with a desktop computer that only has USB mouse/keyboard capability, various user-interface issues and, perhaps more importantly, migrating data from another OS (in my case Linux Mint) to the Qubes environment. By the way, I have Thunderbird set up with Enigmail and have my keys set up using Split GPG. I will be switching tho using the mailing list for submissions. Oh, and I am now using Qubes as my full-time computing environment :-) -- 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/634fcb34-f983-4146-82ce-69e24839491d%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Keyboard and mouse issue (R 4.0.1)
On Wednesday, January 16, 2019 at 1:14:45 AM UTC-6, Ivan Mitev wrote: > On 1/15/19 11:04 PM, John Goold wrote: > > On Tuesday, January 15, 2019 at 9:08:48 AM UTC-6, Ivan Mitev wrote: > >> On 1/15/19 2:42 PM, unman wrote: > >>> On Tue, Jan 15, 2019 at 09:26:31AM +0200, Ivan Mitev wrote: > > > On 1/15/19 3:36 AM, jrg.desk...@gmail.com wrote: > > KEYBOARD > > > > How do I set the "compose" key on the keyboard? I have run several > > Linux distributions (base on Debian/Ubuntu) for several years and have > > had no problems setting a compose key so that I could enter > > diacriticals and symbols like the em-dash and the Spanish upside down > > exclamation and question marks. > > IIRC there's no gui setting in XFCE for setting a compose key. I don't > use such key myself but I guess you can edit dom0's > /etc/X11/xorg.conf.d/00-keyboard.conf and add XkbOptions there (eg. > Option "XkbOptions" "compose:menu"). Run `grep "compose:" > /usr/share/X11/xkb/rules/base.lst` to find what keys you can use. > > >>> > >>> The default key combo is Shift+AltGR - enabled by default in X > >>> You can also set XkbOptions compose: in /etc/default/keyboard > >> > >> I thought that /etc/default/keyboard was only for debian and > >> derivatives. Are you sure it works for fedora ? > > > > First things first :-) When trying out keyboard changes, I wanted them to > > apply globally (they work just fine when I use setxkbmap..., thanks) and so > > made a change in dom0. Since the test change did not seem to work, I > > thought I would try a complete reboot (imagining that when dom0 starts up, > > it reads its configuration files and then doesn't reread them after that). > > Indeed, tweaking X conf files will require a reboot in Qubes OS. With a > standard distribution you'd log off, kill/restart the X server, and log > in again, but if you do so in Qubes OS your VM apps won't be displayed > anymore (not sure if it's a bug or a feature - I never log off anyway so > it doesn't bother me). > > > > What a surprise -- my mouse reverted to being left-handed! I have no idea > > why (other than the reboot) or why it reverted to right-handed (other than > > the sys-usb VM being set up). Any way, the problem has "gone away". > > Magic :) > > > > Now for the keyboard changes. As I indicated, I wanted to turn off the Caps > > Lock key and set a "compose" key. > > > > I launched a dom0 terminal and sudo'ed to root. Then I edited the file > > "/etc/X11/xorg.conf.d/00-keyboard.conf" and added the XkbOptions line. It > > now reads: > > > > Section "InputClass" > > Identifier "system-keyboard" > > MatchIsKeyboard "on" > > Option "XkbLayout" "us" > > Option "XkbOptions" "caps:none" > > EndSection > > > > After rebooting, the Caps Lock key is now off in all Qubes :-) However, I > > am not sure of the syntax of this file and do not want to make an error in > > the file in case it makes my keyboard inactive. > > > > Can I change that last Option line to: > > > > Option "XkbOptions" "caps:none compose:menu" > > > > or do need to use a comma to separate the two options (could not find this > > information in the Wikipedia article) OR, possibly use: > > > > Option "XkbOptions" "caps:none" > > Option "XkbOptions" "compose:menu" > > > > You'll have to use commas - eg. > > Option "XkbOptions" "caps:none,compose:menu" > > In case you mess up your X config and X won't start you should see a > text login prompt instead the graphical login; you can login and fix > conf files from there like you did from a terminal in dom0. Perfect! Now my keyboard settings really are global and, as such things should be, set in one place. Thank you for all the help you have been giving me. -- 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/f4913ca1-6443-4d2a-bacc-bd38b4a7ff99%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Making a Qubes USB Installer USB with Fedora LiveCD
Hey, I am having an Issue putting a qubes 4.0.1-x86_64.iso image onto a Flash Drive. The laptop I am using is Lenovo X1 Carbon Gen 6. I am using the method described here https://www.qubes-os.org/doc/thinkpad-troubleshooting/. Here is my output of the command: [liveuser@localhost ~]$ sudo livecd-iso-to-disk --format --efi /run/media/liveuser/Windows/Users/Alex/Desktop/Qubes-R4.0.1-x86_64.iso /dev/sdc Verifying image... /run/media/liveuser/Windows/Users/Alex/Desktop/Qubes-R4.0.1-x86_64.iso: 9d20945f71a1e4066e742d95cfe61fb5 Fragment sums: d8d4876194afaad8b914cbf9e342df1b73a1578abc8529e135e2b8f6a3fc Fragment count: 20 Supported ISO: no Press [Esc] to abort check. Checking: 100.0% The media check is complete, the result is: PASS. It is OK to use this media. /Packages found, will copy source packages to target. WARNING: This will DESTROY All DATA on: /dev/sdc !! Press Enter to continue, or Ctrl C to abort. Waiting for devices to settle... mkfs.fat 4.1 (2017-01-24) Copying LiveOS image to target device... squashfs.img 411,631,616 100% 342.82MB/s0:00:01 (xfr#1, to-chk=0/1) Syncing filesystem writes to disc. Please wait, this may take a while... Setting up /EFI/BOOT Unable to find an EFI configuration file. I am using Fedora-Workstation-Live-x86_64-29-1.2.iso which I downloaded off of there website and I used Fedora Media Creater to put it on the Flash Drive. Any Ideas as too why I am getting this error. -- 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/9c83502b-b5af-4fad-a21e-38a7ba73c9bf%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] HCL Dell Inspiron 13 5000
After months of dithering, I decided to take the plunge with this machine. Everything works. Touchpad, touchscreen, webcam, audio. Printer recognised and works after running hp-setup. Still a few things to test but I am pleased. Please note, this machine seems to be a UK version. The one on dell.com differs from the one on dell.co.uk. -- 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/85e.5c3f59e3%40qubes-os.info. For more options, visit https://groups.google.com/d/optout. Qubes-HCL-Dell_Inc_-Inspiron_5379-20190116-155614.yml Description: Binary data Qubes-HCL-Dell_Inc_-Inspiron_5379-20190116-160704.cpio.gz Description: GNU Zip compressed data
[qubes-users] HCL - LENOVO Thinkpad P1
Difficult to setup due to the "I219-LM" Network controller needing permissive=true and no-strict-reset=true and unable to install latest nvidia cuda drivers. Kernel-latest and/or Xen 4.8 does not support the Intel UHD GPU even when disabling nouveau - must use Nvidia only for now. Sleep not working with BIOS 1.17 (known issue of all the latest Lenovo Thinkpad models since they removed S1 and S3 from BIOS). Log a support ticket with Lenovo. Tested with 4.0.1 RTM and kernel-latest (4.19). See this post for more debugging information: https://groups.google.com/d/msg/qubes-users/z51dkaEOiqc/wNhQ_86NGQAJ Tip: don't set nomodeset for the Hybrid graphics with blacklisting nouveau - won't work completely. And setting nouveau.modeset=0 nouveau.blacklist=yes or modprobe.blacklist=nouveau will only get you 0.33 Frames Per Second refresh pain which makes the system unusable. Force it to discrete graphics (nvidia) and leave the nouveau for now. Lots of screen flickering with nouveau, and lots of battery drain. This model has 32 GB of ECC ram with the Xeon and p2000, used by the 4K screen. VM sys-usb exists Qubes release 4.0 (R4.0) Brand: LENOVO Model: 20MDCTO1WW BIOS: N2EET35W (1.17 ) Xen:4.8.4 Kernel: 4.19.12-3 RAM:32385 Mb CPU: Intel(R) Xeon(R) E-2176M CPU @ 2.70GHz Chipset: Intel Corporation Device [8086:3ec4] (rev 07) VGA: NVIDIA Corporation Device [10de:1cba] (rev a1) (prog-if 00 [VGA controller]) Net: Intel Corporation Device a370 (rev 10) Intel Corporation Ethernet Connection (7) I219-LM (rev 10) SCSI: HVM:Active I/O MMU:Active HAP/SLAT: Yes TPM:Device not found Remapping: yes -- 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/019643de-e1f5-4c22-9eeb-de505c3ac15f%40googlegroups.com. For more options, visit https://groups.google.com/d/optout. Qubes-HCL-LENOVO-20MDCTO1WW-20190113-140540.yml Description: Binary data
[qubes-users] HCL - LENOVO Thinkpad X1 Tablet 3rd Gen
sys-usb option is disabled during install due to keyboard being USB. Suspend not working due to known Lenovo BIOS issues (they removed S1 and S3). Very simple install overall. Touchscreen/pen input acts as normal mouse like most other touchscreens. Sleep issue is a known issue of all the latest Lenovo Thinkpad models since they removed S1 and S3 from BIOS). You might be able to look at the ACPI tables the Thinkpad Carbon G6 owners are doing and manually edit them on this device to get working. Log a support ticket with Lenovo, because they fixed the Thinkpad Carbon G6 BIOS due to popular demand. -- 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/15397718-7883-4ade-9adc-5702f76c1f7e%40googlegroups.com. For more options, visit https://groups.google.com/d/optout. Qubes-HCL-LENOVO-20KJCTO1WW-20190107-152837.yml Description: Binary data
[qubes-users] HCL - LENOVO Thinkpad X1 Yoga 3rd Gen
Simple install. Most things working except Suspend and "Yoga Mode" not disabling the trackpad nor flipping the monitor. Sleep not working with BIOS 1.17 Sleep issue is a known issue of all the latest Lenovo Thinkpad models since they removed S1 and S3 from BIOS). There are some ACPI hacks for this model posted online to get it working. Log a support ticket with Lenovo, because they fixed the Thinkpad Carbon G6 BIOS due to popular demand. For the beautiful HiDPI screen, I built a custom version of Xrandr in a DVM from master that has the "nearest" filter commit (they haven't released the latest Xrandr in a while). Using the nearest filter allows for a much sharper scaling than the default xrandr. However, it still had a bit of fuzziness for me. I then just switched the resolution to 1368x720 which gave the clearest results (still just a tad fuzzy, but also lost of resolution!). I could not get xrandr working for any VMs though with the virtual display. i3wm is a dream come true on this device. Once installing i3wm, the DPI settings were picked up (maybe my previous hacking, maybe it actually detected it) and things were scaled 100% pixel perfect! Some VMs still have GUI apps that are wrong though for DPI. But close enough. -- 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/683a290b-a5d9-474d-b304-06bdcabd4f41%40googlegroups.com. For more options, visit https://groups.google.com/d/optout. Qubes-HCL-LENOVO-20LD0017US-20190107-232107.yml Description: Binary data
[qubes-users] Re: Re: Re: VMApp files from template
I have not been successful in accessing VMApp files from dom0. So I have bowed to the inevitable and placed my script in the template. Now it works. Thanks for your help, uman. -- 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/85a.5c3f5090%40qubes-os.info. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] "Qubes Update" icon (Sun Looking icon on top right)
Worked like a charm! Opened up "Konsole" in my whonix-14-gw and -ws templates Ran this command: sudo apt install python-concurrent.futures I can now use the Sun/update icon to update my templates. It seemes the benefits are: Starts and stops each template automically, one at at a time Can run the updates in the back ground with out manual intervention Not sure there are other benefits but thanks again!! Keep doing what you folks do! -- 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/0449efa0-22aa-49d5-9b60-1a60a2b757ef%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Follow up on solved HP laptop model 15t-da000 installation -- and a congrats on the new version
I posted a couple of days ago about trying to install a dual boot KDE neon and Qubes OS 4.0.1 on an HP laptop with a hybrid disk system -- 256G SSD and 1T SATA. I had originally thought the problem was solved by installing Qubes first and then KDE neon, since both would come up that way. When I did KDE neon first, and then Qubes, Qubes would not intialize. Unfortunately it wasn't as successful as I thought. Once KDE neon was installed, the windowing system came up in qubes, but nothing worked -- no network, etc, though oddly, the dom0 terminal came up. The only workaround I came up with that works was to install qubesOS and its /boot/efi and /boot on the SSD, and to install KDE neon and its /boot/efi and /boot on the SATA drive, and make both of them bootable. Then I have to choose which drive to boot from in the BIOS menu. That way everything works fine. ... which leads me to my next point. Congrats to the developers on this new version. Now, I have to admit that when I tried out Qubes a few months ago, it was on a box with a traditional SATA drive, and I know that affects response time, but the difference to me on this new box is night and day. The responsiveness of Qubes the first time I set it up was so bad it simply was not viable. This new setup is pretty snappy. I'm sure I'm going to have all sorts of questions as I tweak this for my own use, but I gotta say right off the bat that this is a real, usable system this time around, and not the sandbox "well, this is an interesting idea" kind of thing it seemed a few months ago. Thanks to the developers for an interesting OS that combines security *and* usefulness. -- 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/8a332399-eade-4f49-b3d5-00b5c3636b03%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Keyboard and mouse issue (R 4.0.1)
On Wed, Jan 16, 2019 at 08:31:37AM +0200, Ivan Mitev wrote: > > > > Not really a Fedora person. Probably not. :-( > > On the other hand, I *do* find a GUI way of setting the key under System > > Settings/Keyboard in KDE, and in Xfce, under > > SystemTools-Keyboard-Layout. > > Oh, you're right - as usual :) > I think I've already demonstrated that this is not so. -- 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/20190116120428.azv7gldn7hcuib2e%40thirdeyesecurity.org. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: Re: VMApp files from template
On Wed, Jan 16, 2019 at 04:22:32AM -0500, Dave Albiston wrote: > Thanks for your patience, uman > > It is the exec line that is the problem. In the work domain > I can run the script using: > > sh /home/Scripts/myscript.sh > > I guess that the menu exec statement is being run in dom0. > So how can the statement be changed to point to a file in > the work domain? Or, alternatively, how can the command be > forced to execute in the work domain? > > It's a learning curve! We're all learning. Make the script executable in the work qube. Then in dom0 , try 'qvm-run work /home/Scripts/myscript.sh' at console. Assuming that works, then you have the exec statement to use in the menu item. If it doesnt work, then you can use 'qvm-run -p' to get stdin/out in the console, which may help with troubleshooting. Or start logging in the script to see where it breaks. You can also use '-u ' to run as specified user. Once you can call the command from dom0, use that as the exec line. -- 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/20190116120212.h2pbeq542juihdsh%40thirdeyesecurity.org. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Intel X540-AT2 network card worked in Qubes 3.2, fails in 4.0.1?
Having just installed Qubes 4.0.1 I am not able to get my 10Gb Intel X540-AT2 network card to work. It worked out of the box in Qubes 3.2. This is what I get in the net-vm: $ sudo dmesg |grep ixgbe [2.737931] ixgbe: Intel(R) 10 Gigabit PCI Express Network Driver - version 5.1.0-k [2.737971] ixgbe: Copyright (c) 1999-2016 Intel Corporation. [3.045650] ixgbe :00:06.0: Failed to allocate MSI-X interrupts. Err: -22 [3.045658] ixgbe :00:06.0: Disabling SR-IOV support [3.045665] ixgbe :00:06.0: Disabling RSS support [3.049104] ixgbe :00:06.0: Multiqueue Disabled: Rx Queue count = 1, Tx Queue count = 1 XDP Queue count = 0 [3.181722] ixgbe :00:06.0: MAC: 3, PHY: 0, PBA No: G35632-015 [3.181730] ixgbe :00:06.0: a0:36:9f:83:8c:e0 [3.333064] ixgbe :00:06.0: Intel(R) 10 Gigabit Network Connection [3.347927] ixgbe :00:06.0 ens6f0: renamed from eth0 [3.878232] ixgbe :00:06.0: registered PHC device on ens6f0 The "Failed to allocate MSI-X interrupts" doesn't look very good? The problem is that the network link never becomes ready: $ sudo dmesg |grep link [3.864405] IPv6: ADDRCONF(NETDEV_UP): ens6f0: link is not ready [4.013735] IPv6: ADDRCONF(NETDEV_UP): ens6f0: link is not ready Is this a known problem? What should I try next? -- 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/02989017-eb6f-41e1-ac2b-9a4525301d19%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: Re: VMApp files from template
Thanks for your patience, uman It is the exec line that is the problem. In the work domain I can run the script using: sh /home/Scripts/myscript.sh I guess that the menu exec statement is being run in dom0. So how can the statement be changed to point to a file in the work domain? Or, alternatively, how can the command be forced to execute in the work domain? It's a learning curve! -- 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/854.5c3ef7d8%40qubes-os.info. For more options, visit https://groups.google.com/d/optout.
