[qubes-users] Latest qubes-template-archlinux xorg-server package breaks pacman update completely
Hello, As the title said, the latest xorg-server version (1.19.1-1) on Arch Linux will break the 'qubes-vm-gui' dependency completely. I think there's a need to have these Qubes packages on AUR repository as well instead of just re-compiling the archlinux template again and again. I tried both on the old 'my own compile version' of archlinux template and the one from 'qubes-community-template' repo. I'm not sure if NoUpgrade or IgnorePkg option on /etc/pacman.conf help much in this case, instead I need to remove xf86-input-evdev, xf86-input-libinput, xf86-input-void and xf86-input-joystick first before I can upgrade other packages as well. @Marek do you have any idea on this? -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/CAOCHQOuBhGLrbdXZQSax1G14ajTw4%2BJB6PZgybaDmZSvaLX%2BUg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Is Qubes OS compatilable with Ledger Nano S/Trezor/Keepkey?
On 01/16/2017 12:37 AM, Franz wrote: On Sat, Jan 14, 2017 at 10:39 PM, Marek Marczykowski-Górecki < marma...@invisiblethingslab.com> wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Sat, Jan 14, 2017 at 09:17:32PM +0100, Maksymilian Skica wrote: Hi, Does anyone actually make Qubes OS working with some bitcoin hardware wallet? I want to buy one now and my first requirement is that it will work with Qubes. Yes, it should work using qvm-usb. At least Trezor do work. Also assigning to a Trezor-VM the USB controller of a USB expresscard dedicated to Trezor, it works perfectly. Best Fran - -- 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- Version: GnuPG v2 iQEcBAEBCAAGBQJYetLfAAoJENuP0xzK19csHIMH/ihx8tx2LUGlVgvUSptwa52h Oor7Y/zeaDbeZzDsFCXwca2XVtfhm+idkqehmk6VamYeVRAeVg9iBYGlLWG4sC8M hBsIiz4ZOWBqWokBSRFO72PZDqbwkz6E2cCuWXFanRkPrWfTNFGruf3OjYN52fCC gCLpLWgsAMVEQH4OunrQJSDkBgcIfEobtDwFqxckdGVen/pos+C0sI0DBO8WVQiK y3rw7MRp5X0brRycbVJ531TRsFVK+nZCcFdO4x/aSQDaXIQlm+RfxR6VQQzIjC+c qP3vxy1IbNOGQYPmhQTVIU0BHysT6cJBt58GdUEiLz3u7RYCjMuQvjXPYnfE+P8= =8Z0H -END PGP SIGNATURE- -- 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/20170115013942.GB3974%40mail-itl. For more options, visit https://groups.google.com/d/optout. Am I the only one who thinks it is a horrible idea to use a closed source hardware device designed by a bunch of kids and probably made in china to manage lots of money? Hardware crypto sucks because it can't be verified without a team of PhD's and millions of dollars in equipment. -- 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/0a11315c-f94e-8b9b-9b65-8985bd8034a6%40gmx.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: WHEEL emulation ALPSpS Pointing Stick on Dell E6420 running Qubes 3.2
Am Montag, 2. Januar 2017 08:04:42 UTC+1 schrieb Michael Fliegner: > The following made it work > > xinput --list-props 11 > > xinput --set-int-prop "AlpsPS/2 ALPS DualPointStick" "EvDev Wheel Emulation" > 8 1 No longer works after upgrade to fedora-24. AlpsPS/2 unknown device 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/e74d31c8-fdc9-4610-8a6d-7cda1b268aa4%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Salt / qubesctl errors when configuring USB
On 01/15/2017 08:25 PM, Marek Marczykowski-Górecki wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Sun, Jan 15, 2017 at 08:02:17PM -0500, Chris Laprise wrote: On 01/15/2017 05:02 PM, Marek Marczykowski-Górecki wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Sun, Jan 15, 2017 at 04:10:49PM -0500, Chris Laprise wrote: The salt failure occurs with any type of VM. This may be due to some aspect of my dom0 configuration that changed, because when sys-usb was initially setup the qubesctl commands worked. Care to share actual configuration (including where you've placed it)? The error message clearly is about some file not being found. I didn't mean to suggest I changed it *intentionally*. It could be a bug or a side-effect of something else I did. I have customized dom0 in some ways, such as using the 4.8 kernel and changing auth settings according to the vm-sudo doc. At some point I did upgrade dom0 with 'testing', but later continued updating with stable. Still - I can't help you without seeing actual configuration causing this issue. You've surely modified something, because default configuration don't have any reference to name "qvm.f24-clone.top". The 'qvm.f24-clone' part is supposed to refer to a VM, but I see now that is not the design the 'qvm.sys-usb' is some coded preset that qubesctl uses. Please disregard. Chris -- 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/65c73121-fe29-cc84-5c54-285b043f18c2%40openmailbox.org. For more options, visit https://groups.google.com/d/optout.
[qubes-users] HCL - Dell Latitude E7470
Install and boot went smoothly. Was able to connect to wireless and access the internet. -- 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/1484538198.430266.848742064.6DD985D6%40webmail.messagingengine.com. For more options, visit https://groups.google.com/d/optout. Qubes-HCL-Dell_Inc_-Latitude_E7470-20170111-223321.yml Description: Binary data Qubes-HCL-Dell_Inc_-Latitude_E7470-20170111-223321.cpio.gz Description: GNU Zip compressed data
Re: [qubes-users] Salt / qubesctl errors when configuring USB
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Sun, Jan 15, 2017 at 08:02:17PM -0500, Chris Laprise wrote: > On 01/15/2017 05:02 PM, Marek Marczykowski-Górecki wrote: > > -BEGIN PGP SIGNED MESSAGE- > > Hash: SHA256 > > > > On Sun, Jan 15, 2017 at 04:10:49PM -0500, Chris Laprise wrote: > > > The salt failure occurs with any type of VM. This may be due to some > > > aspect > > > of my dom0 configuration that changed, because when sys-usb was initially > > > setup the qubesctl commands worked. > > Care to share actual configuration (including where you've placed it)? > > The error message clearly is about some file not being found. > > > > I didn't mean to suggest I changed it *intentionally*. It could be a bug or > a side-effect of something else I did. > > I have customized dom0 in some ways, such as using the 4.8 kernel and > changing auth settings according to the vm-sudo doc. At some point I did > upgrade dom0 with 'testing', but later continued updating with stable. Still - I can't help you without seeing actual configuration causing this issue. You've surely modified something, because default configuration don't have any reference to name "qvm.f24-clone.top". - -- 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- Version: GnuPG v2 iQEcBAEBCAAGBQJYfCEkAAoJENuP0xzK19csdzwH/1KPMab5dHquNC3S6WRx9TpA e71loEiBXAl86NuEQBy/H0qKsmSC4rR52r1aBgJ42F0352hSsnh1R00zWfVw5k1b qatFXajDsiq2ADpvY4ftsmTp67n6LfslrTRcIqTMYpZ4KQ2cqUYgxxP7vcmpXCoQ N9mYU9pGa6wVzLeAMihC1Kbt79uIXcZMZjsYqSBtJX6rQjVdk/M0O1tGdPU0C5sR tbmEGVnIcpSR3ELeKQrDfBuXf26oDMZzMKxuCS6X2wwpm6GcgXnQo6tGRuBwSjow PMdciCDj4Qe5p1jJ9qDGya5mergsL8kAfqMSkQ+Y8phSIKKp8nMeSfckIHfk6rg= =pK4e -END PGP SIGNATURE- -- 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/20170116012555.GD5268%40mail-itl. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Salt / qubesctl errors when configuring USB
On 01/15/2017 05:02 PM, Marek Marczykowski-Górecki wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Sun, Jan 15, 2017 at 04:10:49PM -0500, Chris Laprise wrote: The salt failure occurs with any type of VM. This may be due to some aspect of my dom0 configuration that changed, because when sys-usb was initially setup the qubesctl commands worked. Care to share actual configuration (including where you've placed it)? The error message clearly is about some file not being found. I didn't mean to suggest I changed it *intentionally*. It could be a bug or a side-effect of something else I did. I have customized dom0 in some ways, such as using the 4.8 kernel and changing auth settings according to the vm-sudo doc. At some point I did upgrade dom0 with 'testing', but later continued updating with stable. Chris -- 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/0ebfb8f0-67b2-2334-fd0d-c5e06b7a8661%40openmailbox.org. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: Can anyone recommend a video card for Qubes
On Sunday, January 15, 2017 at 12:22:20 AM UTC+3, qmast...@gmail.com wrote: > Saturday, 14 January 2017 г., 14:20:23 UTC-5 tai...@gmx.com wrote: > > On 01/14/2017 12:15 PM, qmastery wrote: > > > > > Saturday, 14 January 2017 г., 5:01:34 UTC-5 Chris Willard написал: > > >> Hello All, > > >> > > >> I am using my on-board video but only getting 1024x768 resolution so > > >> wondered if there is another video card type I could use. > > >> > > >> -- > > >> Best regards, > > >> Chris > > >> > > > any AMD graphic card should be great for Qubes, because AMD has pretty > > > good open source drivers for Linux. Dont get NVIDIA because in that case > > > you would have to use NVIDIA closed source drivers with hidden backdoors > > > and proven telemetry; nouveau is still not in a good shape, probably > > > because no real assistance from NVIDIA - they want everyone to use their > > > closed source stuff > > > > > Wait the nvidia linux drivers have telemetry? > > I thought it was only windows, and only if you install the "geforce > > experience". > > > > Irreguardless nvidia is an awful company that adds "bugs" to nerf > > featuresets on non-windows platforms, and they make it hard to attach > > the card to a virtual machine (ex: error 43). > > > > Just say NO to binary blobbed hardware. > > Yes, you are correct, maybe I am wrong here... After that experience when I > uninstalled a Geforce Experience from my friend's Windows PC, but telemetry > "virus" wasn't removed and continued to work until I wiped those nvidia > telemetry executable files manually using Ubuntu LiveCD - the remains of my > trust to this company has been completely lost. Maybe it is more safe to > assume that their telemetry is in all their software, and the best way to > avoid it is to stop using NVIDIA products. The source is closed, and we just > can't verify with 100% confidence that their latest Linux drivers don't have > a telemetry as well, they had plenty of time to build in telemetry into Linux > drivers and conceal it Well, I gotta warn that chances of successfully working with closed source drivers are slim. They compile okay, and even insmod okay, but X dies with occult error about allocating memory. I am having an almost bearable experience with core i7's integrated graphics 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/43ab8f0e-a72d-4ded-bc7b-ba28b28eb754%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Salt / qubesctl errors when configuring USB
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Sun, Jan 15, 2017 at 04:10:49PM -0500, Chris Laprise wrote: > The salt failure occurs with any type of VM. This may be due to some aspect > of my dom0 configuration that changed, because when sys-usb was initially > setup the qubesctl commands worked. Care to share actual configuration (including where you've placed it)? The error message clearly is about some file not being found. - -- 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- Version: GnuPG v2 iQEcBAEBCAAGBQJYe/FzAAoJENuP0xzK19csl7EH/Aj6U0943iY+e0FU1KQrVLz0 pwHRBURR3D74RXGEm9r8s2w6kun48UkFRC1sOHr88P6g6gREWzf4wCW2B8m7SdUi QebiVtRUm3aRqhtvlj+U5iKT4WlEeIzQ3GIyL4UMmuUh263rwZRu/QU0IUnHrDSr dzaQt3ulwGK2XFIZCzjIJBTxJHErJUtrpEx+M796AOheOrB0T9HapNj/h8t4d0hD Rt5VDgtrRLBTO/auYl/zLmQlzeCXyX10NxJtnmFnxLzfs6SKLG0kWftgR3Aic4jk EM3EhIM+RvDyRh8GYO2ojCCtXUbL9UvSFfYwwCqvrpFkPqorJ1NjbR2moOP+sUs= =be8V -END PGP SIGNATURE- -- 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/20170115220226.GC5268%40mail-itl. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: IPv6 connectivity and qubes proxy VM
On Sunday, January 15, 2017 at 8:23:27 AM UTC+3, Chris Laprise wrote: > On 01/13/2017 04:34 PM, *@gmail.com wrote: > > On Thursday, January 12, 2017 at 1:30:07 PM UTC-5, daltong defourne wrote: > >> On Thursday, January 12, 2017 at 6:47:00 PM UTC+3, daltong defourne wrote: > >>> Hi! > >>> I've created a VPN proxyvm (debian-8 based) according to existing > >>> documentation (more or less - I'm using the VPN provider's standalone > >>> client because, in a VM, why not?) > >>> > >>> For IPv4 it works flawlessly. > >>> > >>> For IPv6 it does not work at all for the VMs "behind" the proxyvm (VPN's > >>> IPv6 support works for a browser launched within proxyvm itself, but any > >>> VM behind the proxyvm can only use IPv4) > >>> > >>> what's up? > >>> Can it be helped? > >> Found this commit. > >> https://github.com/marmarek/qubes-core-agent-linux/commit/789eb511266d9e8bd812e40f952ec2bce6d7a414 > >> > >> Managed to activate the qubes-ipv6 service (worked!) on the appvm, the > >> firewallvm before the proxyvm, and the proxyvm. > >> > >> No budge, IPv6 still missing in action :( > > isn't ipv6 unsafe? You sure this is not by design in qubes? lol. I'm > > probably wrong don't mind me. > > Maybe 'naive' is a better word for ipv6 addressing. > > IIRC, ipv6 won't be officially supported until Qubes Release 4. > > Chris Well, since I plan to move IPv6 only through the VPN (explicitly forbidding forwarding via eth device a-la what is already done for ipv4 in "normal" qubes-vpn-proxyvm documentation to prevent leaks) there are no security/privacy issues for me (beyond risk associated with the VPN itself lol ;-) ) I kind of hoped we'll eventually see v6 in 3.2 too (isn't 3.2 "Qubes LTS"?) https://www.qubes-os.org/news/2016/09/02/4-0-minimum-requirements-3-2-extended-support/ -- 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/ab69fe11-1380-4559-afef-90980299853c%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] HCL - Lenovo ThinkPad X1 Yoga 2016 (20FQ005UGE)
se $# in
1) PART_DEV=$1 ;;
*) usage ;;
esac
if [ "$(id -ur)" != 0 ]; then
log "This command must be run as root!"
exit 1
fi
# examine device
BOOT_MAJMIN=$(mountpoint -d "$BOOT_DIR") || BOOT_MAJMIN=
PART_DEV_MAJMIN=$(lsblk -dnr -o MAJ:MIN "$PART_DEV")
if external "$PART_DEV" && [ "$BOOT_MAJMIN" != "$PART_DEV_MAJMIN" ]; then
alias replace=true
else
alias replace=false
fi
WHOLE_DEV=$(lsblk -dnp -o PKNAME "$PART_DEV")
if ! [ -b "$WHOLE_DEV" -a "$WHOLE_DEV" != "$PART_DEV" ]; then
log "Couldn't find parent device: $WHOLE_DEV"
exit 1
fi
PART_DEV_REAL=$(readlink -f "$PART_DEV")
PART_NUM=${PART_DEV_REAL##*[!0-9]}
if ! [ "$PART_NUM" -gt 0 ]; then
log "Couldn't extract partition number: $PART_NUM"
exit 1
fi
# This check (instead of a more obvious 'mountpoint $BOOT_DIR') should work
# even in unusual setups without any internal boot partition at all:
if [ ! -e "$GRUB_CFG" ]; then
log "Couldn't find boot files at $BOOT_DIR"
exit 1
fi
# keep old label unless overridden explicitly
OLD_LABEL=$(lsblk -dnr -o LABEL "$PART_DEV") ||
OLD_LABEL=
case "$OLD_LABEL" in "$LABEL_PREFIX"*)
if [ -z "${LABEL_SUFFIX+set}" ]; then
LABEL=$OLD_LABEL
fi
esac
# create and/or label fs
if replace; then
log "Creating new ext4 filesystem labeled $LABEL"
mkfs.ext4 $F -L "$LABEL" "$PART_DEV"
else
log "Labeling filesystem $LABEL"
e2label "$PART_DEV" "$LABEL"
fi
# move secrets if label changed
if [ -n "$OLD_LABEL" -a \
-e "$AEM_DIR/$OLD_LABEL" -a \
! -e "$AEM_DIR/$LABEL" ]; then
mv -v "$AEM_DIR/$OLD_LABEL" "$AEM_DIR/$LABEL"
fi
# mount
if CUR_MNT=$(devtomnt "$PART_DEV") && [ -n "$CUR_MNT" ]; then
PART_MNT=$CUR_MNT
else
CUR_MNT=
PART_MNT=/mnt/anti-evil-maid/$LABEL
log "Mounting at $PART_MNT"
mkdir -p "$PART_MNT"
mount "$PART_DEV" "$PART_MNT"
fi
# sync
mkdir -p "$PART_MNT/aem"
mkdir -p "$AEM_DIR/$LABEL"
# make device bootable
if replace; then
log "Setting bootable flag"
parted -s "$WHOLE_DEV" set "$PART_NUM" boot on
log "Copying boot files"
find "$BOOT_DIR" -maxdepth 1 -type f ! -name 'initramfs-*.img' \
-exec cp {} "$PART_MNT" \;
# TODO: If dracut is configured for no-hostonly mode (so we don't have to
# worry about picking up loaded kernel modules), just copy each initramfs
# instead of regenerating it
for img in "$BOOT_DIR"/initramfs-*.img; do
ver=${img%.img}
ver=${ver##*initramfs-}
log "Generating initramfs for kernel $ver"
dracut --force "$PART_MNT/${img##*/}" "$ver"
done
log "Copying GRUB themes"
dst=$PART_MNT/${GRUB_DIR#$BOOT_DIR/}
mkdir "$dst"
cp -r "$GRUB_DIR/themes" "$dst"
log "Installing GRUB"
grub2-install --boot-directory="$PART_MNT" "$WHOLE_DEV"
log "Bind mounting $PART_MNT at $BOOT_DIR"
mount --bind "$PART_MNT" "$BOOT_DIR"
log "Generating GRUB configuration"
grub2-mkconfig -o "$GRUB_CFG"
log "Unmounting bind mounted $BOOT_DIR"
umount "$BOOT_DIR"
fi
if [ -z "$CUR_MNT" ]; then
log "Unmounting $PART_MNT"
umount "$PART_MNT"
fi
Qubes-HCL-LENOVO-20FQ005UGE-20161129-172726.yml
Description: application/yaml
Qubes-HCL-LENOVO-20FQ005UGE-20170115-213858.yml
Description: application/yaml
anti-evil-maid-install.sig
Description: PGP signature
Qubes-HCL-LENOVO-20FQ005UGE-20161129-172726.yml.sig
Description: PGP signature
Qubes-HCL-LENOVO-20FQ005UGE-20170115-213858.yml.sig
Description: PGP signature
Re: [qubes-users] Salt / qubesctl errors when configuring USB
The salt failure occurs with any type of VM. This may be due to some aspect of my dom0 configuration that changed, because when sys-usb was initially setup the qubesctl commands worked. Chris -- 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/6f3bb8f4-7f92-7450-d03a-5dc49aa297ee%40openmailbox.org. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: Prob installing VLC in Fedora24 Template
Saturday, 14 January 2017 г., 12:15:17 UTC-5 Arnulf Maria Bultmann wrote: > > > did you try this? You can remove cached packages by executing 'dnf clean > > > packages' > > > > Yes I tried it several times with the same result > > I solved my problem by downloading the rpm in a appvm and then copying it to > the template vm. But it should work in the template vm without work around. > Or? You could have tried cloning a vlc git repository and compiling it from source https://wiki.videolan.org/UnixCompile/ This way you would have had a more recent vlc 3.0 (rpm which you have installed is from older git revision) BTW there is no stable vlc 3.0 yet, only development versions -- 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/27479c47-48fa-4507-a3b3-a65e028ad4c8%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: MacBook Pro retina 2015
Sunday, 15 January 2017 г., 11:25:56 UTC-5 user Steve wrote: > On Sunday, January 15, 2017 at 3:20:46 AM UTC+4, Andrew Densmore wrote: > > I was planning on installing qubes on my macbook pro 2015 but even if it is > > compatible, is it worth having to deal with all the apparent problems with > > installing on a mac or should I just try to dual boot it on my PC? > > I too would be very interested to know. At the moment I have Qubes nicely > installed on an HP Elitebook but would rather have it on my Mac (and look at > a Hackintosh solution to OSX in a Domain) I tried looking for that "Hackintosh solution" yesterday, OS X in a Domain seems quite hard to accomplish. Cant find any successful reports about running any recent OS X in HVM Xen Domain (macOS Sierra, or El Capitan at least) Someone tried to do it with Snow Leopard, but no luck - http://wiki.osx86project.org/wiki/index.php/Snow_Leopard_Server_on_Xen Seen some instructions about running macOS Sierra in Virtual Box, but sadly Virtual Box can't be used in a Xen environment (and same goes for closed source VMWare) if you have any ideas about how it could be done, please drop them here -- 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/0bc7de9d-a9d8-4ac4-ac0f-3a186e7c3f95%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: MacBook Pro retina 2015
On Sunday, January 15, 2017 at 3:20:46 AM UTC+4, Andrew Densmore wrote: > I was planning on installing qubes on my macbook pro 2015 but even if it is > compatible, is it worth having to deal with all the apparent problems with > installing on a mac or should I just try to dual boot it on my PC? I too would be very interested to know. At the moment I have Qubes nicely installed on an HP Elitebook but would rather have it on my Mac (and look at a Hackintosh solution to OSX in a Domain) -- 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/e974cb46-dd87-4db3-b86f-a9c18515ce9b%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Electrobsd in Qubes
Hi, guyz. What do you think about https://www.fabiankeil.de/gehacktes/electrobsd/ "Anyone who is able to use Tails should eventually be able to install and use ElectroBSD." -- 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/f8a8ecf9-78b4-413f-a32f-e30148b4d6c9%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] DVM savefile creation failed
> On 01/14/2017 10:13 AM, haaber wrote: >> Hello, >> I get the error message in the title when trying to open a DispVM. >> It is my firt try to play with disposable VMs in and out-of-the-box >> install. Where do I find log files on that? Thank you,Bernhard > > You can try manually generating the savefile with this: > dom0$ qvm-create-default-dvm --default-template > > It should complete without errors. > > Chris > Thank you Chris, that did it and showed the problem : I was "out of memory". After closing some VMs it worked perfectly. All the best, Bernhard -- 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/c71b9cb9-84f6-c0ce-b980-1f6043a3a704%40web.de. For more options, visit https://groups.google.com/d/optout.
