[qubes-users] qubes-dom0-update (3.2) failing with error message
Hi, When executing "sudo qubes-dom0-update" in dom0, I'm receiving the following error: tar: /var/lib/qubes/dom0-updates: Cannot open: No such file or directory tar: Error is not recoverable: exiting now Dom0 updates dir does not exists: /var/lib/qubes/dom0-updates I can confirm that the directory does not exist. I do have a backup of dom0. Any pitfalls around restoring dom0? Any help is greatly appreciated. Be well! Doug -- 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/7b2918b2-a1f8-49c2-cf1f-5728a202b492%40riseup.net. For more options, visit https://groups.google.com/d/optout.
[qubes-users] AppVM unexpectedly changes kernel
Recently two appvms refused to start, reporting that: VM: VM kernel does not exist: /var/lib/qubes/vm-kernels/4.4.12-9/vmlinuz Qubes Manager shows the kernel is set to 4.4.38-11. Using 'qvm-prefs myappvm -s kernel 4.4.38.11' fixed the issue. The appvm templates are debian-8 and whonix-ws based. Anything I should be concerned about here? 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/6ae50257-daa6-9337-1a9b-04f86e1793e2%40riseup.net. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: FYI: Experimental Qubes coldkernel support now available
Reg Tiangha: > On 2016-12-19 3:20 PM, Doug Hill wrote: >> >> Thanks for the tip, Marek... The process moved a bit farther along... >> >> I believe I hit the gcc issue that was mentioned eariler; a few >> meaningful-looking snippets are below. Any thoughts are >> appreciated! >> >> >> >> >> CC [M] fs/ncpfs/ioctl.o >> CC drivers/acpi/acpica/utobject.o >> CC drivers/acpi/acpica/utosi.o >> CC drivers/acpi/acpica/utownerid.o >> CC [M] fs/ncpfs/mmap.o >> *** WARNING *** there are active plugins, do not report this as a bug >> unless you can reproduce it without enabling any plugins. >> Event| Plugins >> PLUGIN_FINISH_TYPE | randomize_layout_plugin constify_plugin >> PLUGIN_FINISH_DECL | randomize_layout_plugin >> PLUGIN_FINISH_UNIT | rap_plugin >> PLUGIN_ATTRIBUTES| randomize_layout_plugin >> latent_entropy_plugin size_overflow_plugin constify_plugin >> PLUGIN_START_UNIT| latent_entropy_plugin >> size_overflow_plugin rap_plugin constify_plugin >> PLUGIN_ALL_IPA_PASSES_START | randomize_layout_plugin rap_plugin >> constify_plugin >> In file included from ./include/linux/seqlock.h:35:0, >> from ./include/linux/time.h:5, >> from ./include/linux/stat.h:18, >> from fs/ncpfs/mmap.c:9: >> ../include/linux/spinlock.h:58:0: internal compiler error: Segmentation >> fault >> #include >> ^ >> Please submit a full bug report, >> with preprocessed source if appropriate. >> See for instructions. >> CC drivers/acpi/acpica/utpredef.o >> CC drivers/acpi/acpica/utresrc.o >> The bug is not reproducible, so it is likely a hardware or OS problem. >> scripts/Makefile.build:289: recipe for target 'fs/ncpfs/mmap.o' failed >> make[5]: *** [fs/ncpfs/mmap.o] Error 1 >> scripts/Makefile.build:440: recipe for target 'fs/ncpfs' failed >> make[4]: *** [fs/ncpfs] Error 2 >> Makefile:972: recipe for target 'fs' failed >> make[3]: *** [fs] Error 2 >> make[3]: *** Waiting for unfinished jobs >> CC drivers/acpi/apei/apei-base.o >> > > > Did you install the correct gcc plugin for the Debian template you're > trying to compile this on? According to the coldhak instructions, it'll > either be one of these: > > sudo apt install gcc-4.9-plugin-dev (for GCC 4.9) > sudo apt install gcc-5-plugin-dev (for GCC 5.x) > sudo apt install gcc-6-plugin-dev (for GCC 6.x) > > Stock Debian-8 should be using the 4.9 version unless you have > previously upgraded gcc on that template. > > > Yes, gcc looks like the correct verion (I'm on a stock debian-8 template): user@debian-8-coldkernel:~$ sudo apt install gcc-4.9-plugin-dev Reading package lists... Done Building dependency tree Reading state information... Done gcc-4.9-plugin-dev is already the newest version. 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/28f76743-50cb-9aa4-5645-651e1c8e66b6%40riseup.net. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: FYI: Experimental Qubes coldkernel support now available
Marek Marczykowski-Górecki: > On Sun, Dec 18, 2016 at 04:34:39PM +0000, Doug Hill wrote: > > >> Colin Childs: >>> Hi everyone, >>> >>> Sorry for not getting on this list sooner, however it looks like testing >>> of coldkernel on Debian is largely going well! I see the most recent >>> issue from foppe, and will be attempting to reproduce later this evening. >>> >>> If you run into issues that require coldhak attention, please do not >>> hesitate to open tickets at >>> https://github.com/coldhakca/coldkernel/issues, or email us directly at >>> cont...@coldhak.ca. >>> >>> Thanks, and happy testing! >>> > >> Hi, > >> Running into a problem when runnning "make qubes-guest" on a stock >> debian-8 template. > >> Below are the last few lines of the output. Thanks! > >> CC [M] fs/xfs/xfs_buf_item.o >> CC [M] fs/xfs/xfs_extfree_item.o >> CC [M] fs/xfs/xfs_icreate_item.o >> CC [M] fs/xfs/xfs_inode_item.o >> CC [M] fs/xfs/xfs_rmap_item.o >> CC [M] fs/xfs/xfs_log_recover.o >> CC [M] fs/xfs/xfs_trans_ail.o >> CC [M] fs/xfs/xfs_trans_buf.o >> CC [M] fs/xfs/xfs_trans_extfree.o >> CC [M] fs/xfs/xfs_trans_inode.o >> CC [M] fs/xfs/xfs_trans_rmap.o >> CC [M] fs/xfs/xfs_sysctl.o >> CC [M] fs/xfs/xfs_ioctl32.o >> LD [M] fs/xfs/xfs.o >> LD fs/built-in.o >> scripts/package/Makefile:97: recipe for target 'bindeb-pkg' failed >> make[2]: *** [bindeb-pkg] Error 2 >> Makefile:1317: recipe for target 'bindeb-pkg' failed >> make[1]: *** [bindeb-pkg] Error 2 >> make[1]: Leaving directory '/home/user/coldkernel/linux-4.8.13' >> Makefile:61: recipe for target 'qubes-guest' failed >> make: *** [qubes-guest] Error 2 >> user@debian-8-coldkernel:~/coldkernel$ > > Relevant error is probably earlier. I guess it's about disk space - it > require 4GB or so to build. > > Thanks for the tip, Marek... The process moved a bit farther along... I believe I hit the gcc issue that was mentioned eariler; a few meaningful-looking snippets are below. Any thoughts are appreciated! CC [M] fs/ncpfs/ioctl.o CC drivers/acpi/acpica/utobject.o CC drivers/acpi/acpica/utosi.o CC drivers/acpi/acpica/utownerid.o CC [M] fs/ncpfs/mmap.o *** WARNING *** there are active plugins, do not report this as a bug unless you can reproduce it without enabling any plugins. Event| Plugins PLUGIN_FINISH_TYPE | randomize_layout_plugin constify_plugin PLUGIN_FINISH_DECL | randomize_layout_plugin PLUGIN_FINISH_UNIT | rap_plugin PLUGIN_ATTRIBUTES| randomize_layout_plugin latent_entropy_plugin size_overflow_plugin constify_plugin PLUGIN_START_UNIT| latent_entropy_plugin size_overflow_plugin rap_plugin constify_plugin PLUGIN_ALL_IPA_PASSES_START | randomize_layout_plugin rap_plugin constify_plugin In file included from ./include/linux/seqlock.h:35:0, from ./include/linux/time.h:5, from ./include/linux/stat.h:18, from fs/ncpfs/mmap.c:9: ./include/linux/spinlock.h:58:0: internal compiler error: Segmentation fault #include ^ Please submit a full bug report, with preprocessed source if appropriate. See for instructions. CC drivers/acpi/acpica/utpredef.o CC drivers/acpi/acpica/utresrc.o The bug is not reproducible, so it is likely a hardware or OS problem. scripts/Makefile.build:289: recipe for target 'fs/ncpfs/mmap.o' failed make[5]: *** [fs/ncpfs/mmap.o] Error 1 scripts/Makefile.build:440: recipe for target 'fs/ncpfs' failed make[4]: *** [fs/ncpfs] Error 2 Makefile:972: recipe for target 'fs' failed make[3]: *** [fs] Error 2 make[3]: *** Waiting for unfinished jobs CC drivers/acpi/apei/apei-base.o -- 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/8f5ea8f0-1a6e-2c7b-9c9c-cd779f350f6a%40riseup.net. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: FYI: Experimental Qubes coldkernel support now available
Colin Childs: > Hi everyone, > > Sorry for not getting on this list sooner, however it looks like testing > of coldkernel on Debian is largely going well! I see the most recent > issue from foppe, and will be attempting to reproduce later this evening. > > If you run into issues that require coldhak attention, please do not > hesitate to open tickets at > https://github.com/coldhakca/coldkernel/issues, or email us directly at > cont...@coldhak.ca. > > Thanks, and happy testing! > Hi, Running into a problem when runnning "make qubes-guest" on a stock debian-8 template. Below are the last few lines of the output. Thanks! CC [M] fs/xfs/xfs_buf_item.o CC [M] fs/xfs/xfs_extfree_item.o CC [M] fs/xfs/xfs_icreate_item.o CC [M] fs/xfs/xfs_inode_item.o CC [M] fs/xfs/xfs_rmap_item.o CC [M] fs/xfs/xfs_log_recover.o CC [M] fs/xfs/xfs_trans_ail.o CC [M] fs/xfs/xfs_trans_buf.o CC [M] fs/xfs/xfs_trans_extfree.o CC [M] fs/xfs/xfs_trans_inode.o CC [M] fs/xfs/xfs_trans_rmap.o CC [M] fs/xfs/xfs_sysctl.o CC [M] fs/xfs/xfs_ioctl32.o LD [M] fs/xfs/xfs.o LD fs/built-in.o scripts/package/Makefile:97: recipe for target 'bindeb-pkg' failed make[2]: *** [bindeb-pkg] Error 2 Makefile:1317: recipe for target 'bindeb-pkg' failed make[1]: *** [bindeb-pkg] Error 2 make[1]: Leaving directory '/home/user/coldkernel/linux-4.8.13' Makefile:61: recipe for target 'qubes-guest' failed make: *** [qubes-guest] Error 2 user@debian-8-coldkernel:~/coldkernel$ -- 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/dec89517-4cbf-91af-b3a5-7414918e77c7%40riseup.net. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] R3.2 rc2 blank screen - screenlock issue?
richard.f.go...@gmail.com: > Problem description: > > After using the system all day (including unlocking and unlocking the > screen just fine) and then leaving it overnight I come back to a > blank screen. > > Doing a Ctrl-Alt-F2 gives me a command prompt but I can't get X to > respond (with Ctrl-Alt-F1). > > After a reboot all is well until after some apparently random period > it happens again. > > I've gone through the screen locker and power management settings in > Xfce (turned power management off) and turned of power management in > BIOS. No joy. > > System spec: Qubes RC2 rc2 running Xfce on Intel NUC5i5YRH with 16G > ssd. Kde is also installed but I'm not using it. > > Has anyone got a solution? -- Richard > Hi, I'm having a similar issue, which I believe may be caused by a bug in xfce. I posted about it here in a previous thread: https://groups.google.com/d/msg/qubes-users/qwMzj2au6uE/qd_hU6EUBQAJ Best of luck! -- 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/305ca12c-ce33-aee2-64c7-3586f7f9a5d7%40riseup.net. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] external screen issue - hdmi switch no longer works with Qubes R3.2
Patrick Schleizer: > Marek Marczykowski-Górecki: >> On Sat, Jul 02, 2016 at 05:07:00PM +, Patrick Schleizer wrote: >>> Since dom0 was upgraded to R3.2 [on my test system], multi monitoring >>> got worse. (It is not #2084 [1].) >> >>> I need to manually set to the external display now every time (in KDE), >>> but I could life with that. >> >>> What is worse... That my HDMI switch that used to work fine with R3.1 >>> (and still does on my main system) is now broken in R3.2. Direct hdmi >>> connection however still works. Both, KDE and XFCE are affected by that. >> >> Can you elaborate on this? What exactly is the effect? > > R3.1 > - if external screen is directly connected: visible in monitor settings > and functional > - if external screen is to a HDMI switcher first and then indirectly to > the computer: visible in monitor settings and functional > > R3.2 > - if external screen is directly connected: visible in monitor settings > and functional > - if external screen is to a HDMI switcher first and then indirectly to > the computer: not visible in monitor settings and no monitor signal > >>> In XFCE monitor settings menu I did once see the external screen flash >>> up for a second and then vanish again. >> >>> Any idea how to fix that? >> >>> Cheers, >>> Patrick >> >>> [1] https://github.com/QubesOS/qubes-issues/issues/2084 >> >> >> > Hi, I'm having a similar issue, but in my case, with a direct HDMI1 connection, my monitor will not wake from sleep. After some searchng, I discovered this may be caused by a known bug in xfce. I was able to replicate this behavior under Mint 18 xfce on the same machine. xfsettingsd resets TV mode to NULL on power cycle Bug: https://bugzilla.xfce.org/show_bug.cgi?id=11107 In comment #67, dated 2016-08-12, a patch appears on its way. This is a new world for me, and a translation would be appreciated... I'm guessing the patch eventually works its way through the system... how long does that take? Many thanks, Doug -- 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/22d5b190-a489-91ec-395e-e461be44331a%40riseup.net. For more options, visit https://groups.google.com/d/optout.
[qubes-users] HCL and 3.2RC1 observations
New user to Qubes over the last few months. Many thanks to the developers for creating this clever OS, and the users who have contributed to this group. My setups were smoother as a result! I've been successfully using 3.1 on a T420. Attached is a HCL for System76's Meerkat. Nice little machine, but appears to have only one USB controller, so keyboard, mouse, USB drives are all in dom0. Under 3.2RC1, the only major issue I'm having (on the meerkat) is this (under xfce): If I manually turn off my external HDMI monitor, or if system suspends it, upon powering it back up, the monitor reports "no signal." I have to reboot the machine... Turning off suspend is my short term solution. This situation did NOT occur on the T420, RC1, xfce, and VGA. I tried using KDE, and essentially the same error occurred, but KDE returned the following before becoming unstable: "Executable plasmashell PID: 4007 Signal: Segmentation fault (11)" Confirming the below bug report in RC1: Enigmail 1.9 is incompatible with Split GPG on Debian 8 https://github.com/QubesOS/qubes-issues/issues/2170 In my case, "vault" is stock fedora-23 and client is gently modified whonix-ws. Worked under 3.1, VMs migrated to RC1 by backup/restore. Happy to provide any further debugging info, just please be explicit in your directions as I'm a noob at the command line in linux. Thanks, Doug -- Doug Hill AB77 9B0D F85F 786E 2276 3CF1 8F88 AE89 13E2 89F6 -- 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/98b75bd6-56e7-651d-b0bc-06a7e76bb1ce%40riseup.net. For more options, visit https://groups.google.com/d/optout. Qubes-HCL-System76__Inc_-Meerkat-20160717-083155.yml Description: application/yaml signature.asc Description: OpenPGP digital signature
