Re: [qubes-users] 3.2-rc3 Dom0 Update gives False Flags
On Sat, 24 Sep 2016 08:40:03 +, amadaus <amad...@riseup.net> wrote: > VM Manager sends out regular notifications that Dom0 updates are > available - this is what you'd expect. However, in approximately 50% > of these cases, there are no available updates. > This is what happens after a notification is received: In VM Manager > ---> click download ---> Dom0 qubes manager opens dialogue box saying > checking for updates > Sys-Firewall box opens saying downloading > ---> dialogue boxes close and VM Manager update flag disappears. > > These false flags happen about once/day. > > Anyone else getting similar symptoms? Hi, I have the same issue - notification and update icon shows out, but qubes-dom0-update says it has nothing to do. Executing qubes-dom0-update removes icon for some time. -- yaqu -- 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/20160924102529.9E5C7104F62%40mail2.openmailbox.org. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Available memory
On Thu, 29 Sep 2016 08:06:43 -0700 (PDT), raahe...@gmail.com wrote: > ah yes xlinfo, i learned of this command when trying to find a way to > show how much memory the system recognizes installed. BTW you could also use dmidecode (in dom0): $ sudo dmidecode|grep 'Range Size' > In 3.0 all memory was loaded by dom0. So I would just watch the > qubes-manager and make sure missing memory from dom0 matched up to > total of the vms. But since 3.1 though dom0 is limited to 4gb so > accounting for all the memory manually that way is not possible > anymore. If you need it, you can switch it back by removing dom0_mem parameters from /etc/default/grub, rebuilding grub config: $ sudo grub2-mkconfig -o /boot/grub2/grub.conf and rebooting. -- yaqu -- 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/20160929183145.8867C20C991%40mail.openmailbox.org. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: Why should I verify digests, if I already checked PGP signatures?
On Mon, 3 Oct 2016 16:13:03 -0700 (PDT), jkitt <jazzkitte...@gmail.com> wrote: > On Saturday, 1 October 2016 14:07:32 UTC+1, Arqwer wrote: > > Documentation says to check digests after I verified an .iso with > > gpg. Why? Doesn't correct PGP signature mean, that .iso is good and > > came from Qubes developers? > > Yes it does. Normally distros sign the digest. Qubes signs the iso. To be precise: Qubes signs both, the iso and the digest. -- yaqu -- 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/20161004090647.F2DBF205303%40mail.openmailbox.org. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] How to trim AppVm's data to match the correct size inside?
On Sun, 9 Oct 2016 06:19:47 -0700 (PDT), 8c36b1b85a745a25508d01ced9335bef7a1e4ed1 <necroku...@gmail.com> wrote: > I have delete a lot of big datas on one of my appvm, but the problem > is the size doesn't change eventhough 'df -h' in the appvm shows that > the user's data already decreased. Qubes-Manager and dom0 still > recognised its size with the old values. How can i proceed to > decrease it? Procedure should be similar to compacting templates: https://www.qubes-os.org/doc/fedora-template-upgrade-21/#compacting-the-upgraded-template Inside VM fill unused space on private.img with zeros: [user@untrusted ~]$ dd if=/dev/zero of=/home/user/zero [user@untrusted ~]$ rm /home/user/zero And then copy image in dom0: [user@dom0 ~]$ qvm-shutdown --wait untrusted [user@dom0 ~]$ cd /var/lib/qubes/appvms/untrusted/ [user@dom0 ~]$ cp --sparse=always private.img private.img.new [user@dom0 ~]$ mv private.img.new private.img But I have just noticed, that after removing big files in appvm, its private.img has been automagically compacted, without using this procedure. Tested on R3.2 and fedora23-based appvm. -- yaqu -- 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/20161009145409.299AD200228%40mail.openmailbox.org. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: R3.2-rc3: hotplugging ExpressCard devices
On Sun, 18 Sep 2016 19:40:49 +0200, yaqu <qubesus...@openmailbox.org> wrote: > Hello, > > After upgrading from R3.0 to R3.2-rc3, I am no longer able to hotplug > ExpressCard devices (e.g. USB 3.0 adapter). Is it a bug or feature? > > When I connect adapter to running Qubes, nothing happens - it is not > detected, not reported by lspci, also there is nothing in dmesg. > > When I boot Qubes with already connected adapter, it is properly > detected, attached to dom0, and works fine. But if I disconnect it, > it is still reported by lspci as connected. > > As a workaround, I have to manually rescan PCI bus after connecting > adapter: > $ sudo sh -c 'echo 1 > /sys/bus/pci/rescan' > > And manually remove it after disconnecting: > $ sudo sh -c 'echo 1 > /sys/bus/pci/devices/:05:00.0/remove' > > It works, but it is not very handy :-( I'm resending this mail, it looks like it was filtered out or stuck in moderation queue... Meanwhile, I've found out it's a feature: https://github.com/QubesOS/qubes-issues/issues/1673 -- yaqu -- 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/20160919132332.BE1D4202637%40mail.openmailbox.org. For more options, visit https://groups.google.com/d/optout.
[qubes-users] R3.2-rc3: hotplugging ExpressCard devices
Hello, After upgrading from R3.0 to R3.2-rc3, I am no longer able to hotplug ExpressCard devices (e.g. USB 3.0 adapter). Is it a bug or feature? When I connect adapter to running Qubes, nothing happens - it is not detected, not reported by lspci, also there is nothing in dmesg. When I boot Qubes with already connected adapter, it is properly detected, attached to dom0, and works fine. But if I disconnect it, it is still reported by lspci as connected. As a workaround, I have to manually rescan PCI bus after connecting adapter: $ sudo sh -c 'echo 1 > /sys/bus/pci/rescan' And manually remove it after disconnecting: $ sudo sh -c 'echo 1 > /sys/bus/pci/devices/:05:00.0/remove' It works, but it is not very handy :-( Regards, -- yaqu -- 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/20160918174059.6C803202186%40mail.openmailbox.org. For more options, visit https://groups.google.com/d/optout.
[qubes-users] R3.2-rc2: random reboots on Lenovo T520 (workaround)
After upgrade from R3.0 to R3.2-rc2, my T520 started rebooting randomly a few times a day. Sometimes after 10 minutes of running, sometimes after 12 hours, but always with nothing in logs. After a long and boring investigation I have found out it was triggered by connecting external monitor and it can be fixed by disabling the Intel i915 RC6 feature (some power saving stuff). Since I've added i915.enable_rc6=0 as a kernel parameter (GRUB_CMDLINE_LINUX in /etc/default/grub) I have a 50 hours of uptime and counting :-) Affected hardware: Lenovo ThinkPad T520 cpu: Intel(R) Core(TM) i5-2520M CPU @ 2.50GHz chipset: Mobile Intel QM67 Express gpu: Intel HD Graphics 3000 Relevant results from lspci: 00:00.0 Host bridge: Intel Corporation 2nd Generation Core Processor Family DRAM Controller (rev 09) 00:02.0 VGA compatible controller: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller (rev 09) Qubes 3.2-rc2, kernel 4.4.14-11 Does anyone else have similar issue with i915? -- yaqu -- 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/20160922213719.41769103DFC%40mail2.openmailbox.org. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Can TeamViewer or similar work with Qubes..?
On Thu, 22 Sep 2016 11:05:10 -0700 (PDT), neilhard...@gmail.com wrote: > I am working on a project with someone. > > And they want to remote into Qubes with TeamViewer. > > Will this work at all... or is there any alternative software..? TeamViewer installed in AppVM can be used only as a client - you can connect to someone's desktop. It works, I use it very often. If you want someone to connect to your desktop, try to install it in HVM. You should be able to share VM's desktop (but not the whole Qubes). I've tested it in Windows 7 HVM once and it worked. -- yaqu -- 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/20160922183837.AD9452037E5%40mail.openmailbox.org. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] System still freezes, still no resolution.
On Wed, 28 Sep 2016 02:20:35 -, johnyju...@sigaint.org wrote: > A bit late to the party (as they say) in this discussion, but why is > it so important to suspend/restore in the first place? [...] > For a laptop on the go, okay, I can see the argument. But I don't > think most Qubes users are on laptops, given the hardware > requirements. (Very much moreso with 4.0. :P) Correct me if I'm > wrong. Yes, it's for laptops. Using laptop at home and in the office, and commuting every day, makes suspend/restore very useful feature. Hibernate would be even better, but it's not supported by Qubes. Qubes on laptops are not rare, according to published HCLs. And Qubes-compatible laptop doesn't have to be expensive - e.g. used Thinkpad T520 with i5-2520M for $200 and 16 GB RAM for $110 is really affordable. And I hope it will also run Qubes 4.0, since it supports SLAT/EPT (well, according to specs). -- yaqu -- 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/20160928132829.28AF2101528%40mail2.openmailbox.org. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Qubes OS 3.2 has been released!
On Fri, 30 Sep 2016 14:06:14 -0300, Franz <169...@gmail.com> wrote: > On Fri, Sep 30, 2016 at 1:56 PM, <raahe...@gmail.com> wrote: > > I just did a clean install from a usb. restored my vms and custom > > templates from my 3.1 backup everything working good. > > > > thanks, I was really wondering if it was possible to restore 3.1 > templates. Documentation only mentions applVMs Upgrading templates is documented there: https://www.qubes-os.org/doc/upgrade-to-r3.2/ BTW I was restoring my fedora templates from R3.0 to R3.2 and it worked well. All I had to do was upgrade templates to 3.1, then upgrade to 3.2, and then install missing packages: $ sudo dnf install qubes-upgrade-vm $ sudo dnf update $ sudo dnf install qubes-upgrade-vm $ sudo dnf update $ sudo dnf install qubes-img-converter qubes-input-proxy-sender qubes-mgmt-salt-vm-connector qubes-usb-proxy Regards, -- yaqu -- 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/20161002195955.DFEA2106F09%40mail2.openmailbox.org. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Qubes 3.2 - TeamViewer not connecting
On Fri, 28 Oct 2016 19:39:38 -0500, Vincent Elliott <vincent.c.elli...@gmail.com> wrote: > Am very new to Qubes OS and am trying to get TeamViewer v11 working. > The problem is it will not connect and is requesting proxy settings. > > Anyone had any success with this? TeamViewer works for me (of course as client only) very well (versions 9, 10 and now 11): https://groups.google.com/d/msg/qubes-users/55FLgq801_w/8IqgeZdVBQAJ -- yaqu -- 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/20161029190551.9C57E104A74%40mail2.openmailbox.org. For more options, visit https://groups.google.com/d/optout.
[qubes-users] HCL - Lenovo Thinkpad T520 (4243WM2)
Hello, I have been using this Thinkpad T520 for 1.5 years with Qubes R2, R3.0 and now R3.2 without major hardware issues (not tested with R3.1). Well, I had a problem with Intel gfx and R3.2, but it's fixed now (details somewhere below). Long story short: it works. CPU: i5-2520M 2.50GHz VT-x: works VT-d: works SLAT/EPT: supported TPM: present, not tested RAM: it had only 4 GB in factory configuration, documentation says it supports max 8 GB, but in fact it supports up to 16 GB of RAM (2*8). GPU: integrated Intel HD Graphics 3000, works, but: Under R3.2, i915.enable_rc6=0 needs to be added to kernel parameters to prevent random reboots when external monitor is connected, as described there: https://groups.google.com/d/msg/qubes-users/DSFcUer3C7M/Rbno0VdfBQAJ Suspend/resume: works. Sound: works Microphone: works Ethernet: Intel 82579LM Gigabit, works Wi-Fi: Intel Centrino Ultimate-N 6300, works Card reader: Ricoh PCIe SDXC/MMC Controller, works Firewire: Ricoh R5C832 PCIe IEEE 1394 Controller, works Display: TFT 15.6" 1600x900, anti-glare Docking station: tested with Lenovo 4338, works Bluetooth: BCM2045B, detected as USB device, but not tested Camera: not present Fingerprint reader: not present Keyboard, trackpoint and touchpad: work There are additional function keys, most of them work, at least these used by me: volume control, mute, LCD dim and keyboard light. ExpressCard/34 port: works, but without hotplugging, as it is not supported by Qubes anymore: https://groups.google.com/d/msg/qubes-users/JVOpOrOPvZk/5Xar5LS8BwAJ USB: two USB 2.0 controllers. One with 2 ports and all internal devices (bluetooth, docking station and its USB ports), and second with just 2 ports. Controllers have shared RMRRs, but they can be assigned to different appVMs if these VMs have pci_strictreset=false. Note: since upgrade to R3.2 I'm no longer able to assign USB controller to Win7 HVM. For USB 3.0 I use ExpressCard adapter (on Renesas uPD720202 chipset) and it works well. AFAIR I had to disable power management for pccard in BIOS. All communication ports or devices can be disabled in BIOS: network cards, bluetooth, modem, USB ports, firewire, ExpressCard slot, eSATA port, ultrabay (CD/HDD), card reader, camera, microphone and fingerprint reader. Some of these ports/devices are not present in this model of T520. There is also the physical switch for disabling bluetooth and Wi-Fi, it also works. -- yaqu -- 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/20161106165033.B27892022D9%40mail.openmailbox.org. For more options, visit https://groups.google.com/d/optout. Qubes-HCL-LENOVO-4243WM2-20161002-222153.yml Description: application/yaml
[qubes-users] R3.2, xfce, resume and changing resolution issues
Hello, When I work on laptop with lid closed and external monitor connected, and when I suspend Qubes, reconnect it to another docking station with different monitor, and wake it up, then screen on external monitor has old resolution, not matching resolution of currently connected monitor. Is it possible to force (or politely convince) xfce4 to autodetect resolution after wake up from suspend? Just like it used to work on KDE? As a workaround I use custom script in /usr/lib/systemd/system-sleep/ that executes on wake up: xrandr --output HDMI1 --auto --output HDMI2 --auto It works, but maybe there is a better solution? And there is a second issue with changing screen resolution. When I change resolution from lower to higher, some icons in tray at the bottom of the screen are not accessible - no tooltip on hoover, no response to click. It looks like only icons of appVM apps are affected (NetworkManager, Psi, Remmina, KeePass...), and icons of dom0 apps work correctly (volume control, power manager, qubes manager). Tray needs to be on bottom of screen, of course. I have found out that to make these icons work again, I have to switch on or off any of connected displays. This issue can be reproduced even without external monitors. Assuming laptop's LCD is on LVDS1, one needs to switch it to some low resolution and then back to default: [user@dom0 ~]$ xrandr --output LVDS1 --mode "800x600"; sleep 3; xrandr --output LVDS1 --auto Now icons are not accessible. To fix it one needs to turn LCD off and on: [user@dom0 ~]$ xrandr --output LVDS1 --off; xrandr --output LVDS1 --auto BTW now as I tested it, it looks that not only tray icons are not accessible. The bottom half of the screen is not clickable for appVM applications. Regards, -- yaqu -- 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/20161106223414.10544103B33%40mail2.openmailbox.org. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] How to check Qubes Debian TVM status?
On Sat, 26 Nov 2016 06:40:07 -0800 (PST), Pawel Debski <pdeb...@econsulting.pl> wrote: > Folks, > > I am not familiar with Debian. What is the best way to check its > exact version $ cat /etc/debian_version > and installed Qubes packages? Not sure if it's the best way, but: $ dpkg -l|grep qubes -- yaqu -- 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/20161126161906.2C4F8104A27%40mail2.openmailbox.org. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] qubes 3.2 windows 10 as "template vm" does not boot anymore. How to do forensics on the image
On Mon, 28 Nov 2016 12:48:10 -0800 (PST), ludwig jaffe <ludwig.ja...@gmail.com> wrote: > As there are production data on the windows10 I want to know how to do > forensics here and recover the data. > There are no mountable file images. What to do? [...] > Any ideas? > -boot? > -forensics (at least)? Are you sure the are no mountable images? You should be able to attach images to other VM, something like this (in dom0): $ qvm-block -A work -f xvdi dom0:/var/lib/qubes/appvms/win7/root.img $ qvm-block -A work -f xvdj dom0:/var/lib/qubes/appvms/win7/private.img And then in VM (here: in a fedora-based appvm): $ sudo fdisk -l /dev/xvdi $ sudo fdisk -l /dev/xvdj $ sudo mount /dev/xvdi1 /mnt/disk1 $ sudo mount /dev/xvdi2 /mnt/disk2 $ sudo mount /dev/xvdj1 /mnt/disk3 That should give you access to your files. -- yaqu -- 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/20161128212720.7FC0D104509%40mail2.openmailbox.org. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] How to check Qubes Debian TVM status?
On Sat, 26 Nov 2016 09:35:59 -0800 (PST), Pawel Debski <pdeb...@econsulting.pl> wrote: > user@debian-8:~$ cat /etc/deb*ver* > 8.6 > > is the newest version I guess Correct, 8.6 is currently the latest 'stable' release. https://www.debian.org/releases/ > and for the Qubes mark I take: > > ii qubes-core-agent 3.2.10-1+deb8u1amd64 > > great, tx. > Not sure however what these two iis at the beginning of the line mean. First character shows the desired state of package, and second shows its current state. "ii" means package should be installed and it is installed. More details you can find in manual: $ man dpkg-query -- yaqu -- 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/20161126212307.6D18F207007%40mail.openmailbox.org. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Trouble upgrading template VMs FC23 -> FC24
On Thu, 17 Nov 2016 05:16:12 -0800 (PST), Pawel Debski <pdeb...@econsulting.pl> wrote: > I have upgraded dom0 as described in > https://www.qubes-os.org/doc/upgrade-to-r3.2/ and than executed: > > sudo dnf install --refresh qubes-upgrade-vm > sudo dnf upgrade --refresh > sudo dnf install qubes-mgmt-salt-vm-connector > > apparently everything went ok, however the template vm still is in > version FC3: You have just upgraded your template to Qubes 3.2, not to Fedora 23. > > What shall I do to actually upgrade it to FC24? Now follow this instruction: https://www.qubes-os.org/doc/fedora-template-upgrade-23/ -- yaqu -- 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/20161117150200.EE98B106849%40mail2.openmailbox.org. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: Fedora 24 template available for Qubes 3.2
On Wed, 16 Nov 2016 01:14:24 +0100, Marek Marczykowski-Górecki <marma...@invisiblethingslab.com> wrote: > On Wed, Nov 16, 2016 at 12:28:17AM +0100, yaqu wrote: > > > You have tried to remove fedora-23 using dnf, while some appVMs > > > still were using it as a template. Dnf has displayed an error, > > > but also it has removed package, leaving it in qubes config (and > > > not cleaning template's directory). > > > > Anyway, I think it should be considered as a bug. > > > > Steps to reproduce (assuming fedora-23-minimal is not installed): > > > > $ sudo qubes-dom0-update qubes-template-fedora-23-minimal > > $ qvm-create -t fedora-23-minimal -l red test-vm > > $ sudo dnf remove qubes-template-fedora-23-minimal > > Yes, you're right. Previously (before Fedora introduced DNF), failure > in %preun script aborted the operation, now it results just in a > message. Not sure if this is a bug of a feature of DNF... Removing package using plain rpm gives the same result, so it's not dnf's fault. There is an interesting entry in rpm changelog: * Fix %preun scriptlet not aborting package erase http://rpm.org/wiki/Releases/4.13.0 So it's fixed in rpm 4.13.0, but in dom0 we have broken rpm 4.13.0-rc1. BTW it was fixed in commit: https://github.com/rpm-software-management/rpm/commit/1ac507f15f014e69b926a1c2bf9a46a2a4dcaff3 And broken in: https://github.com/rpm-software-management/rpm/commit/f4a49c3d446bb180ca6b30a4337065fb6511e641 -- yaqu -- 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/20161116103152.2327120562A%40mail.openmailbox.org. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] R3.2, xfce, resume and changing resolution issues
On Sun, 13 Nov 2016 22:23:08 +0100, Marek Marczykowski-Górecki <marma...@invisiblethingslab.com> wrote: > > Thanks, executing qubes-monitor-layout-notify works as a workaround > > - it is much cleaner solution than hack with switching displays off > > and on :) > > Actually this tool is called automatically when monitor layout is > changed (see watch-screen-layout-changes process). The problem is a > race condition - it is called before new configuration is actually > applied, so it sends the old configuration again... I haven't found > yet any way to receive notification _after_ new configuration is > applied. Any idea? Monitoring relevant X Window events with xev in dom0: $ xev -root -event randr -event structure and changing display settings, shows that after increasing resolution XRROutputChangeNotifyEvent is not sent (only RRScreenChangeNotify, XRRCrtcChangeNotifyEvent and ConfigureNotify), at least on my machine (R3.2, Intel gfx and Xfce). Watch-screen-layout-changes monitors only OutputChange events, and that's why it doesn't detect change and doesn't execute qubes-monitor-layout-notify. I think it would be better to monitor RRScreenChangeNotify event, as it is always sent after changing display settings and it's supported in any randr version (no need to use ConfigureNotify). I have prepared a fix and a pull request. -- yaqu -- 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/20161118145240.E97CE2079C6%40mail.openmailbox.org. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: Fedora 24 template available for Qubes 3.2
On Sun, 13 Nov 2016 12:30:25 -0800 (PST), Grzesiek Chodzicki <grzegorz.chodzi...@gmail.com> wrote: > W dniu niedziela, 13 listopada 2016 20:54:06 UTC+1 użytkownik yaqu > napisał: > > > > It looks like you do not have this package installed (or you have > > executed this command in VM instead of dom0). > > > > To get a list of templates installed from rpm in dom0, you can use > > this command: > > [user@dom0 ~]$ rpm -qa | grep template > > I did execute it in dom0, fedora-23 was installed by default when I > installed Qubes on my PC. Please, check if your fedora-23 template was really installed from rpm (and it wasn't cloned from previous version and upgraded to f23): [user@dom0 ~]$ qvm-prefs fedora-23 | grep rpm installed_by_rpm : True You can also check this using Qubes VM Manager (in VM settings, tab Basic, under "General"). If your fedora-23 template was not installed from rpm, you can remove it using Qubes VM Manager or using command: [user@dom0 ~]$ qvm-remove fedora-23 -- yaqu -- 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/20161113222608.AC803103F86%40mail2.openmailbox.org. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: Fedora 24 template available for Qubes 3.2
On Sun, 13 Nov 2016 11:23:35 -0800 (PST), Grzesiek Chodzicki <grzegorz.chodzi...@gmail.com> wrote: > Following error message is printed after running sudo dnf remove > qubes-template-fedora-23: "No match for argument: > qubes-template-fedora-23 Error: No packages marked for removal." It looks like you do not have this package installed (or you have executed this command in VM instead of dom0). To get a list of templates installed from rpm in dom0, you can use this command: [user@dom0 ~]$ rpm -qa | grep template -- yaqu -- 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/20161113195405.77E2A104967%40mail2.openmailbox.org. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] How to block template vm? (prevent it from starting)
On Sat, 19 Nov 2016 09:27:39 -0800 (PST), Pawel Debski <pdeb...@econsulting.pl> wrote: > is it possible to somehow block a TemplateVM and all VMs based on > this template? > > I.e. whenever some app would be started in any VM involving this > template I'd like to get an error messages or at least have the > operation fail silently instead of having Qubes start the VM. You could add to rc.local script: shutdown -h now VM will shutdown immediately after starting. -- yaqu -- 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/20161119221651.D6182105E9B%40mail2.openmailbox.org. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: Fedora 24 template available for Qubes 3.2
On Tue, 15 Nov 2016 23:06:48 +0100, yaqu <qubesus...@openmailbox.org> wrote: > You have tried to remove fedora-23 using dnf, while some appVMs still > were using it as a template. Dnf has displayed an error, but also it > has removed package, leaving it in qubes config (and not cleaning > template's directory). Anyway, I think it should be considered as a bug. Steps to reproduce (assuming fedora-23-minimal is not installed): $ sudo qubes-dom0-update qubes-template-fedora-23-minimal $ qvm-create -t fedora-23-minimal -l red test-vm $ sudo dnf remove qubes-template-fedora-23-minimal -- yaqu -- 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/20161115232831.1615C2052A4%40mail.openmailbox.org. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Xscreensaver not working when app-menu is open
On Sun, 30 Oct 2016 03:28:39 -0700 (PDT), "Mike A." <andersen.m...@gmail.com> wrote: > But if I open the application menu band then close the lid, the > screensaver does not kick in. When I open the lid later, I can start > using the machine just where I left it. > > I am running Qubes 3.2 with Xfce. > > Can anyone else recreate this, or is it just a problem locally here > (user error at my end)? I have tested it on Lenovo T520 (R3.2, Xfce) and got the same behaviour - closing lid has no effect while appmenu is opened. I have tested it with various settings in Xfce Power Manager (lock screen, suspend, switch off display). When appmenu is closed, closing lid works as expected. Additionally, locking screen manually (Ctrl-Alt-L) doesn't work too while appmenu is opened. -- yaqu -- 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/20161030144820.EEFB5104434%40mail2.openmailbox.org. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: 3.2 installation crash on a ThinkPad
On Mon, 10 Oct 2016 01:49:07 -0700 (PDT), pixel fairy <pixelfa...@gmail.com> wrote: > On Thursday, October 6, 2016 at 1:47:02 AM UTC-7, jkitt wrote: > > I'm trying to install 3.2 on a ThinkPad T420S but the installation > > seems to crash while booting. The kernel boot log display is > > distorted (see pic) and the system seems to hang. > > > > Does 3.2 work on the T420? Is it a graphical thing - can I disable > > it with a kernel parameter? > > this seems to work on a lot of thinkpads. > > https://www.qubes-os.org/doc/thinkpad_x201/ It looks like T420s has the same graphics as T520 (Intel HD 3000). I had a problem with this GPU and R3.2 (random reboots) and I have solved it by adding i915.enable_rc6=0 to kernel parameters: https://groups.google.com/forum/#!msg/qubes-users/DSFcUer3C7M/Rbno0VdfBQAJ BTW with iommu=no-igfx my T520 didn't boot at all. -- yaqu -- 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/20161010100704.C6F84102138%40mail2.openmailbox.org. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Templates: can a template be replaced by another with the same name?
On Thu, 1 Dec 2016 14:10:08 -0800, Andrew David Wong <a...@qubes-os.org> wrote: > > 1. delete the cloned template. > > > > 2. clone fedora23 again onto a new clone using EXACTLY the same > > name as the first clone that was deleted in step 1. > > > > Question: > > > > - the existing AppVMs that are already based on a template with > > that name, will they now just continue to work against the new > > clone, or is there anything else than the template NAME that > > affects the link between AppVMs and their templates? > > > > Qubes won't let you delete a template while AppVMs are still based on > it. You'll have to temporarily switch those one or two AppVMs to a > different template, delete the one you don't want, clone the one you > want, then switch them to the new clone. Or, to avoid switching AppVM's template multiple times, one could: 1. clone template (under temporary name) 2. switch AppVMs to the new template 3. delete the old template 4. rename cloned template to the final name -- yaqu -- 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/20161201230316.75908207459%40mail.openmailbox.org. For more options, visit https://groups.google.com/d/optout.
