Re: [qubes-users] Seamless mode and resize windows doesn't work in a new Windows HVM
> > Are you sure the qubes tools are installed correctly in the new HVM? I > remember it took me a few tries. Also, what happens if you clone the old > one instead of building new? If the clone works, you could try > reinstalling Windows Home inside it and see what happens. Well, I tried to reinstall the qubes win tools several times. Maybe there is a bug in the new version of the qubes video driver. But I don't know how to obtain a previous version of qubes tools to test using a previous version of the qubes video driver. About reinstalling Windows over a clone of my previous VM. I tried, but unfortunately Windows doesn't allow to install a Windows Home version over a Windows Ultimate. -- 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/3e2d3c01-1b39-4650-b240-1de9c75b6f9f%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Seamless mode and resize windows doesn't work in a new Windows HVM
Hi people, I created a new Windows 7 HVM and installed the qubes tools, but the seamless mode doesn't work, and without the seamless mode option selected I can't resize or maximize the window. I have another Windows 7 HVM that I created several months ago and that is working fine in seamless mode or maximizing the window display without the seamless mode. I remember that when I created the previous HVM I didn't need the workaround about the cirrus display driver. Maybe something changed in Qubes since that installation. Another difference with this new HVM is the Windows 7 version: -Old HVM (where the seamless mode works fine): Windows 7 Ultimate (Spanish edition) -New HVM: Windows 7 Home Basic (Spanish edition) I compared the conf files of the HVMs and they have the same configuration, obviously at the exception of the disk file names and IP address. What could be the reason that this functionality isn't working in the new HVM? -- 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/12ee18e8-6ca3-4b97-a5a7-89b5738b7a9f%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] USB Mouse not detected after last upgrade on 3.2
I found the problem. When I updated the template I uninstalled Thunderbird, and the qubes-usb-proxy and other related tools are considered unused dependencies. I think that this is a bug in the template. I solved the issue installing the necessary packages. $ sudo dnf remove thunderbird Dependencies resolved. == Package Arch Version Repository Size == Removing: thunderbird x86_64 52.4.0-2.fc26 @updates 157 M Removing dependent packages: python-backports-ssl_match_hostname noarch 3.5.0.1-4.fc26 @fedora 18 k python2-crypto x86_64 2.6.1-14.fc26 @fedora 2.2 M python2-cryptography x86_64 2.0.2-2.fc26@updates 2.6 M python2-jinja2 noarch 2.9.6-1.fc26@fedora 3.6 M python2-pyOpenSSLnoarch 16.2.0-6.fc26 @updates 523 k python2-requests noarch 2.13.0-1.fc26 @fedora 409 k python2-tornado x86_64 4.4.2-3.fc26@fedora 3.9 M python2-urllib3 noarch 1.20-1.fc26 @fedora 536 k python2-zmq x86_64 16.0.2-3.fc26 @fedora 1.6 M qubes-mgmt-salt-vm-connector noarch 3.2.5-1.fc26 @qubes-builder-vm-r3.2-current-testing 4.7 k qubes-vm-recommended noarch 3.2.3-1.fc26 @qubes-builder-vm-r3.2-current-testing 0 salt noarch 2017.7.2-1.fc26 @updates 36 M salt-ssh noarch 2017.7.2-1.fc26 @updates 3.0 k thunderbird-qubesx86_64 1.2.9-1.fc26 @qubes-builder-vm-r3.2-current-testing 11 k zeromq x86_64 4.1.6-3.fc26@fedora 671 k Removing unused dependencies: PyYAML x86_64 3.12-3.fc26 @fedora 646 k dnf-utilsnoarch 2.1.5-1.fc26@updates 3.8 k libtomcrypt x86_64 1.17-31.20160123git912eff4.fc26 @updates 824 k libtommath x86_64 1.0-8.fc26 @updates 106 k libyaml x86_64 0.1.7-2.fc26@fedora 121 k openpgm x86_64 5.2.122-8.fc26 @fedora 317 k python-backports x86_64 1.0-9.fc26 @fedora 638 python-chardet noarch 2.3.0-3.fc26@fedora 1.1 M python-enum34noarch 1.1.6-1.fc26@fedora 232 k python-ipaddress noarch 1.0.16-4.fc26 @fedora 227 k python2-asn1crypto noarch 0.23.0-1.fc26 @updates 924 k python2-babelnoarch 2.3.4-5.fc26@fedora 20 M python2-backports_abcnoarch 0.5-3.fc26 @fedora 30 k python2-futures noarch 3.1.1-1.fc26@fedora 91 k python2-idna noarch 2.5-1.fc26 @fedora 563 k python2-markupsafe x86_64 0.23-13.fc26@fedora 83 k python2-msgpack x86_64 0.4.8-3.fc26@fedora 272 k python2-pysocks noarch 1.6.7-1.fc26@updates 79 k python2-singledispatch noarch 3.4.0.3-7.fc26 @fedora 46 k python2-systemd x86_64 234-1.fc26 @fedora 262 k pytz noarch 2016.10-4.fc26 @fedora 185 k qubes-core-vm-docnoarch 3.2.20-1 @qubes-builder-vm-r3.2-current-testing 2.2 k qubes-gpg-split x86_64 2.0.26-1.fc26 @qubes-builder-vm-r3.2-current-testing 59 k qubes-img-converter x86_64 1.2.3-1.fc26 @qubes-builder-vm-r3.2-current-testing 6.5 k qubes-input-proxy-sender x86_64 1.0.10-1.fc26 @qubes-builder-vm-r3.2-current-testing 18 k qubes-pdf-converter x86_64 2.1.2-1.fc26 @qubes-builder-vm-r3.2-current-testing 15 k qubes-usb-proxy noarch 1.0.11-1.fc26 @qubes-builder-vm-r3.2-current-testing 7.7 k Transaction Summary =
Re: [qubes-users] USB Mouse not detected after last upgrade on 3.2
> That's a wireless mouse isn't it and what you see there is the USB > receiver? You may be right that it isn't triggering the input proxy. > > When you say "upgrade" do you mean that or simply "update"? I mean are > you still running 3.2? > What template are you using for the sys-usb? What were you using before? > > unman Right, it is a wireless Mouse. I see the receiver Sorry, it was just an update. I am using fedora-26 template. Using this same template was working fine before the dom0 & template update. The rest of usb devices like usb drives or network adapter are working fine and recognized by the Qubes manager. -- 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/dc16e217-ddc8-478b-abce-9de03f1f07c9%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] USB Mouse not detected after last upgrade on 3.2
Hi, After the last upgrade of Qubes + QubesVMs my usb mouse is not working. If I run lsusb in sys-usb I can see the device, but apparently is not detected as a mouse, I think. [user@sys-usb ~]$ lsusb Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 005 Device 002: ID 8087:8000 Intel Corp. ... Bus 002 Device 009: ID 04f2:0976 Chicony Electronics Co., Ltd ... The dom0 file /etc/qubes-rpc/policy/qubes.InputMouse has the line for the device: sys-usb dom0 allow,user=root I restarted the VM and the host machine but the problem persists. Which could be the reason? -- 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/4c079309-4dd9-4e73-896f-740e327fd629%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: Crossover (Office 2016) and Qubes 4rc3
Hi, I am using Crossover on Qubes 3.2. I suppose that it have to work fine in Qubes 4. You just have to install it and register on the template VM, like any other software. After that you can install the Windows apps in the App VM because they are installed in the user home dir -- 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/281f50b1-ce34-4c2b-9ce0-1b147dc2c132%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Yubikey SHA1 challenge-response doesn't match with the openssl result
Hi, I am following the proposed configuration for 2 factor authentication from: https://www.qubes-os.org/doc/yubi-key/ But it isn't working for me. I found that the reason is that the responses from yubikey and from openssl doesn't match. I used the yubikey personalization GUI to configure the key, this is the configuration: Challenge-Response: HMAC-SHA1,12/10/17 5:17 PM,2,,,d574183f4b63995b077987f14457ab19f194c710,,,0,0,0,0,0,0,0,0,1,1 But when I manually test it using a random input, the result doesn't match: Open SSL: $ echo 56508ce98a10825321744c1e0565706f44bd585081d22ba5261836c45eabf14f92f2956b90fcb4eb058c380b8929518b365e28e926464f68707a6831a2eab8fe | xxd -r -ps | openssl dgst -sha1 -macopt hexkey:d574183f4b63995b077987f14457ab19f194c710 -mac HMAC -r | cut -f1 -d ' ' Result: 48e6c79fcb8f5f0dde68e26d646d2908b22321a1 Yubikey: $ ykchalresp -2 -x 56508ce98a10825321744c1e0565706f44bd585081d22ba5261836c45eabf14f92f2956b90fcb4eb058c380b8929518b365e28e926464f68707a6831a2eab8fe Result: 9f7d86c78ccdc232fcbec48e37fe2ac1f3f53a61 I double checked the slot, algorithm used, etc. And I also tried using different keys Where I am wrong? -- 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/3e81779a-9663-4b13-abac-33c2fbae207a%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Whonix update error in Qubes 3.2, release file expired
Hi, When I try to update my Whonix gateway I have the following error: user@host:~$ sudo apt-get update Hit http://deb.whonix.org jessie InRelease Hit http://deb.qubes-os.org jessie InRelease E: Release file for http://deb.whonix.org/dists/jessie/InRelease is expired (invalid since 4h 5min 45s). Updates for this repository will not be applied. user@host:~$ I tried to clean the cache, change the URL protocol to https, but the error continues. Any ideas? -- 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/db4f84a7-487c-4ce2-8f4a-8b102e4b520c%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: Touchscreen not working on Qubes 3.2
Same issue with Dell precision M3800. This was working in previous versions of Qubes, 3.1 I think. -- 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/03654db4-88c5-4b6b-bdd8-37b5505cbe0c%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Reboot a VM that is connected as net/proxy VM
Hi, Yes, I agree It isn't a critical issue, but is too annoying to restore the VMs connections after this type of situations -- 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/e35cb52f-d646-4531-bdf5-4795c5bc47f1%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: Network Manager: 'Device not ready' after suspend.
Hi, I had the same issue, and the workaround metioned by Reg worked for me: https://www.qubes-os.org/doc/wireless-troubleshooting/#automatically-reloading-drivers-on-suspendresume Maybe there are two differen issues. Just to be sure, do you restarted the sys-net after modify the /rw/config/suspend-module-blacklist file? -- 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/5cc0c7b1-b614-474a-ab5b-6472f022bf99%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: Networking two VM
Hi, You just have to start the secure shell server and enable a few rules in iptables. Check the section "Enabling networking between two qubes" in https://www.qubes-os.org/doc/firewall/ Regards -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/349a43b4-b743-4ec6-abc0-8e90a7a3e9c3%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Qubes 3.2 Dom0 no longer updating.
Same issue here. I tried changing the updateVM but it's the same. -- 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/e0ab0e98-d69c-4fa9-af11-2bf790033c05%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Network manager applet icon not visible in KDE plasma systray - Fedora 24/25 VM
Hi, I created a new sys-net VM based on Fedora-24 template. The network works fine but the systray applet icon isn't visible. If I click the mouse over the systray space I can see the menu, connect to the wifi, etc. Something is wrong with the icon. The icon is visible in XFCE, so I think that is some issue in the new version of the Network Manager Applet respect to the KDE systray. The network manager applet version in Fedora-25 is 1.4.0 and 1.0.10 for Fedora-23. I created a new template VM Fedora-25, but the issue persists. Any ideas? -- 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/216995b5-445a-4661-9019-eac28c26efa1%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Broken dependencies in plasma desktop dom0 - qubes 3.2
Thanks The problem in the repo was solved today Regards -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/beff98f4-073f-4c12-8a97-8be15de9c059%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Broken dependencies in plasma desktop dom0 - qubes 3.2
El jueves, 8 de diciembre de 2016, 16:04:12 (UTC-6), Andrew David Wong escribió: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA512 > > On 2016-12-08 07:15, Adrian Rocha wrote: > > Hi, > > > > I updated dom0. I see that there is updated the plasma desktop, but the > > update process reports many packages with broken dependencies: > > > > Are you using (or attempting to use) KDE in dom0 on Qubes 3.2? If so, > it's possible that this is why you have a lot of (what appear to me to > be) KDE-related broken dependencies. One option you might want to > investigate is to group install KDE. Things change rather quickly in > the Fedora/KDE world, so I'm not sure which command they're using > nowadays, but it's probably one of these (or similar): > > $ sudo qubes-dom0-update @kde > $ sudo qubes-dom0-update @kde-desktop > $ sudo qubes-dom0-update --action=groupinstall "KDE Software Compilation" I'm using KDE plasma since the beginning of Qubes 3.2 I installed from the qubes repo with: $ sudo qubes-dom0-update @kde-desktop-qubes It worked perfectly up today. In addition to the broken dependencies. I'm worried about the stability. Why this massive update in repo qubes 3.2? It is supposed that the fc-23 on dom0 will be just in qubes 4, right? > > Note that this will probably pull a *lot* of KDE stuff into dom0, so > be sure that you're aware of the risks before doing this. > > - -- > Andrew David Wong (Axon) > Community Manager, Qubes OS > https://www.qubes-os.org > -BEGIN PGP SIGNATURE- > > iQIcBAEBCgAGBQJYSdjIAAoJENtN07w5UDAwd1wQAMMQ+aOkRIWnoLx+pwq+wiLs > sK2JJqtJ45BoazFOyCnYU44fEtiRNeS1FNQJxufJARq/bQ1MtBs+vXowDBuYVpDl > zHTSWp0BCy6s5DX9ipLxBFkOsipjrR7un4Skfhglk44D/vyJnss4Tb6UxqBZpnBN > mnZ7KVfwErzCr/TbKPkMlBeAsCFpK/0VXBC4ogKQ6NJd6DhWukDeM0U4vQjl9MCg > 8bYvN7USB8aL2bU3mv25g4VJuRAEg9C5FymyG8ChBgAMPUsr3qF7AcfdbdV5q2Vq > XwDX+xA6uz9RYdpwanKAfeULgB8OVVwGBWD3PaXJgxtec9BcCmleR+l8vQgBkGL9 > L491leh1Y2rmDxwylAZpL9p5che8JiEpaZbT9GOPvKBaligVtdun9dNlPAx5Qncr > iGxgCtNU9dUo8TdO15tv3HFWlbtji7hxLsPhnP4E5aT3sBmXO0k0BvWC1OQ4XByL > MJsWbIUyiPcZvxccU/sP8799ZvLdlgKMIIFfGnlDy+74rfQc6IOCdQyyH4+jCqe1 > s8enMe12Nhi84FsFpN2PNLw0vsUqiRw+O7e5HsSfqInY0CNKq1CK/BWZbBDg4ITr > Yw+xWeOlMCieskBDqNJrw3wpElDV9kQPdWcgyZSpHaZpRRKyylHghHFB7C7IKpmQ > nAS/N8opcy95UsYN8wf8 > =nc4Y > -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/ae5eb22d-6b4f-48ba-a08a-735288a002d9%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Broken dependencies in plasma desktop dom0 - qubes 3.2
Hi, I updated dom0. I see that there is updated the plasma desktop, but the update process reports many packages with broken dependencies: Qubes OS Repository for Dom0 88 MB/s | 233 kB 00:00 Dependencies resolved. == Package Arch Version Repository Size == Upgrading: breeze-icon-theme noarch 5.27.0-2.fc23 qubes-dom0-cached 4.0 M dnsmasq x86_64 2.76-2.fc23 qubes-dom0-cached 297 k kf5-atticax86_64 5.27.0-1.fc23 qubes-dom0-cached 169 k kf5-baloo x86_64 5.27.0-1.fc23 qubes-dom0-cached 177 k kf5-baloo-libsx86_64 5.27.0-1.fc23 qubes-dom0-cached 219 k kf5-bluez-qt x86_64 5.27.0-1.fc23 qubes-dom0-cached 196 k kf5-filesystemx86_64 5.27.0-1.fc23 qubes-dom0-cached 15 k kf5-frameworkintegration x86_64 5.27.0-1.fc23 qubes-dom0-cached 1.5 M kf5-frameworkintegration-libs x86_64 5.27.0-1.fc23 qubes-dom0-cached 31 k kf5-kactivities-libs x86_64 5.27.0-1.fc23 qubes-dom0-cached 118 k kf5-kactivities-stats x86_64 5.27.0-1.fc23 qubes-dom0-cached 94 k kf5-karchive x86_64 5.27.0-1.fc23 qubes-dom0-cached 99 k kf5-kauth x86_64 5.27.0-1.fc23 qubes-dom0-cached 123 k kf5-kbookmarksx86_64 5.27.0-1.fc23 qubes-dom0-cached 161 k kf5-kcmutils x86_64 5.27.0-1.fc23 qubes-dom0-cached 302 k kf5-kcodecs x86_64 5.27.0-1.fc23 qubes-dom0-cached 159 k kf5-kcompletion x86_64 5.27.0-1.fc23 qubes-dom0-cached 117 k kf5-kconfig-core x86_64 5.27.0-1.fc23 qubes-dom0-cached 271 k kf5-kconfig-gui x86_64 5.27.0-1.fc23 qubes-dom0-cached 48 k kf5-kconfigwidgetsx86_64 5.27.0-1.fc23 qubes-dom0-cached 376 k kf5-kcoreaddons x86_64 5.27.0-1.fc23 qubes-dom0-cached 354 k kf5-kcrashx86_64 5.27.0-1.fc23 qubes-dom0-cached 33 k kf5-kdbusaddons x86_64 5.27.0-1.fc23 qubes-dom0-cached 67 k kf5-kdeclarative x86_64 5.27.0-1.fc23 qubes-dom0-cached 262 k kf5-kded x86_64 5.27.0-1.fc23 qubes-dom0-cached 76 k kf5-kdelibs4support x86_64 5.27.0-1.fc23 qubes-dom0-cached 2.2 M kf5-kdelibs4support-libs x86_64 5.27.0-1.fc23 qubes-dom0-cached 819 k kf5-kdesu x86_64 5.27.0-1.fc23 qubes-dom0-cached 90 k kf5-kdnssdx86_64 5.27.0-1.fc23 qubes-dom0-cached 99 k kf5-kdoctools x86_64 5.27.0-1.fc23 q
[qubes-users] Re: Intel Wifi not detected in network manager debian net-vm
Solved with: https://groups.google.com/d/msg/qubes-users/BJRnCNcDtoo/QUXiHApxBQAJ Regards -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/0f714b81-1c63-4c04-990e-b4a65c97b7ee%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Intel Wifi not detected in network manager debian net-vm
Hi, I'm trying to setup a debian based net-vm, I assigned the hardware and installed the firmware, but the network manager doesn't see the interface. user@sys-net:~$ ip a 1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever user@sys-net:~$ lspci 00:00.0 Network controller: Intel Corporation Wireless 7260 (rev 6b) user@sys-net:~$ sudo modinfo iwlwifi filename: /lib/modules/4.4.31-11.pvops.qubes.x86_64/kernel/drivers/net/wireless/iwlwifi/iwlwifi.ko license:GPL author: Copyright(c) 2003- 2015 Intel Corporation description:Intel(R) Wireless WiFi driver for Linux firmware: iwlwifi-100-5.ucode firmware: iwlwifi-1000-5.ucode firmware: iwlwifi-135-6.ucode firmware: iwlwifi-105-6.ucode firmware: iwlwifi-2030-6.ucode firmware: iwlwifi-2000-6.ucode firmware: iwlwifi-5150-2.ucode firmware: iwlwifi-5000-5.ucode firmware: iwlwifi-6000g2b-6.ucode firmware: iwlwifi-6000g2a-5.ucode firmware: iwlwifi-6050-5.ucode firmware: iwlwifi-6000-4.ucode firmware: iwlwifi-7265D-13.ucode firmware: iwlwifi-7265-13.ucode firmware: iwlwifi-3160-13.ucode firmware: iwlwifi-7260-13.ucode firmware: iwlwifi-8000-13.ucode ... -- 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/e4fe7ccc-37e6-46f8-b61c-530bd18ea878%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Can TeamViewer or similar work with Qubes..?
Hi, You can install TeamViewer, SSH or any other remote access tool in the VMs. And obviously the VM needs internet access to use the tool, you cannot access to dom0/host or unconnected VMs. To access maybe you need to redirect a port in the firewall depending on the remote access tool that you are using: https://www.qubes-os.org/doc/qubes-firewall/#tocAnchor-1-1-4 Another option is hide the service in TOR by whonix, but you have to consider the connection speed. -- 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/c2034c1b-6908-4a63-8623-35b6d94c9e82%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: Persistant routes on Qubes are not persistant?!
Hi, Did you try adding the commands in /rw/config/qubes-firewall-user-script file, as is indicated in the documentation? https://www.qubes-os.org/doc/qubes-firewall/ Regards El sábado, 22 de octubre de 2016, 12:54:54 (UTC-6), 4oe3ad+c69...@guerrillamail.com escribió: > Unfortunately this Mialing list seems dead. > I've opened this issue, that is specific to the Qubes architecture, for over > a week now and so far no one was able to pinpoint to the solution or explain > why static routes are being overwritten on boot. > > It seems that this ML is only breathing, beacuse of the individual effort of > its users. To the date, no one from the official team > (https://www.qubes-os.org/team/) was able to chip in or give any answer. > > This is a bad start for this project, lack of support is one of the reasons > why some projects are not successful.. > > And to think I was about to give some donations for this project > > > > > > > Sent using Guerrillamail.com > Block or report abuse: > https://www.guerrillamail.com/abuse/?a=UFR2AB5NVqcQmh2U93EQdRjCStifx8dDiadNcQ%3D%3D -- 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/b1f81c8d-ec22-4fa2-ae75-977b378b3588%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Routing network traffic in sys-usb using multiple devices
El lunes, 29 de agosto de 2016, 20:18:51 (UTC-6), Marek Marczykowski-Górecki escribió: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA256 > > On Thu, Aug 18, 2016 at 10:34:55AM -0700, Adrian Rocha wrote: > > El jueves, 18 de agosto de 2016, 10:50:14 (UTC-6), Marek > > Marczykowski-Górecki escribió: > > > -BEGIN PGP SIGNED MESSAGE- > > > Hash: SHA256 > > > > > > On Thu, Aug 18, 2016 at 09:12:35AM -0700, Adrian Rocha wrote: > > > > El jueves, 18 de agosto de 2016, 9:45:44 (UTC-6), Marek > > > > Marczykowski-Górecki escribió: > > > > > -BEGIN PGP SIGNED MESSAGE- > > > > > Hash: SHA256 > > > > > > > > > > On Thu, Aug 18, 2016 at 08:25:34AM -0700, Adrian Rocha wrote: > > > > > > El viernes, 12 de agosto de 2016, 2:34:52 (UTC-6), Marek > > > > > > Marczykowski-Górecki escribió: > > > > > > > -BEGIN PGP SIGNED MESSAGE- > > > > > > > Hash: SHA256 > > > > > > > > > > > > > > On Thu, Aug 11, 2016 at 11:07:54AM -0700, Adrian Rocha wrote: > > > > > > > > Hi, > > > > > > > > > > > > > > > > I have two network devices and one only USB controller, so both > > > > > > > > devices are in the same VM (sys-usb). I want to route some > > > > > > > > app-VMs by one network and the rest by the other network, for > > > > > > > > that I have created two firewall VMs but both are connected to > > > > > > > > the same network VMs because, as I commented, I can not divide > > > > > > > > the network devices in different VMs. > > > > > > > > By default all the traffic is going by only one network device. > > > > > > > > This is the configuration in my sys-usb: > > > > > > > > > > > > > > > > [user@sys-usb ~]$ ip route list > > > > > > > > default via 172.20.1.1 dev enp0s0u2 proto static metric 100 > > > > > > > > default via 192.168.8.1 dev enp0s0u3 proto static metric 101 > > > > > > > > 10.137.4.8 dev vif2.0 scope link metric 32750 > > > > > > > > 10.137.4.29 dev vif9.0 scope link metric 32743 > > > > > > > > 172.20.0.0/21 dev enp0s0u2 proto kernel scope link src > > > > > > > > 172.20.2.255 metric 100 > > > > > > > > 192.168.8.0/24 dev enp0s0u3 proto kernel scope link src > > > > > > > > 192.168.8.100 metric 100 > > > > > > > > > > > > > > > > The firewall IPs are 10.137.4.8 and 10.137.4.29 > > > > > > > > > > > > > > > > I know how to route a traffic to an specific IP using "ip route > > > > > > > > add" to a determined device network, but How can I route the > > > > > > > > complete traffic from one firewall VM by one device network and > > > > > > > > the traffic from other firewall VM by the other device network? > > > > > > > > > > > > > > Source based-routing is tricky in Linux in general. You can > > > > > > > search for > > > > > > > some guides on the internet. > > > > > > > > > > > > > > But alternatively, on Qubes R3.2, you can assign one of those USB > > > > > > > devices to different VM - some separate netvm, or even one of > > > > > > > those > > > > > > > firewallvms directly (and do not attach this firewallvm to any > > > > > > > netvm). > > > > > > > It may work slightly slower, but should be much easier. > > > > > > > > > > > > Thanks for your tip Marek, but I am having an error with the USB > > > > > > assign: > > > > > > > > > > > > The ethernet adapter in the sys-usb VM: > > > > > > [user@sys-usb ~]$ lsusb > > > > > > ... > > > > > > Bus 005 Device 002: ID 0b95:1790 ASIX Electronics Corp. AX88179 > > > > > > Gigabit Ethernet > > > > > > ... > > > > > > > > > > > > And when I try to assing them to the sys-net VM in dom0: > > > > > > [user@dom0 ~]$ qvm-usb > > >
Re: [qubes-users] Routing network traffic in sys-usb using multiple devices
El jueves, 18 de agosto de 2016, 10:50:14 (UTC-6), Marek Marczykowski-Górecki escribió: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA256 > > On Thu, Aug 18, 2016 at 09:12:35AM -0700, Adrian Rocha wrote: > > El jueves, 18 de agosto de 2016, 9:45:44 (UTC-6), Marek > > Marczykowski-Górecki escribió: > > > -BEGIN PGP SIGNED MESSAGE- > > > Hash: SHA256 > > > > > > On Thu, Aug 18, 2016 at 08:25:34AM -0700, Adrian Rocha wrote: > > > > El viernes, 12 de agosto de 2016, 2:34:52 (UTC-6), Marek > > > > Marczykowski-Górecki escribió: > > > > > -BEGIN PGP SIGNED MESSAGE- > > > > > Hash: SHA256 > > > > > > > > > > On Thu, Aug 11, 2016 at 11:07:54AM -0700, Adrian Rocha wrote: > > > > > > Hi, > > > > > > > > > > > > I have two network devices and one only USB controller, so both > > > > > > devices are in the same VM (sys-usb). I want to route some app-VMs > > > > > > by one network and the rest by the other network, for that I have > > > > > > created two firewall VMs but both are connected to the same network > > > > > > VMs because, as I commented, I can not divide the network devices > > > > > > in different VMs. > > > > > > By default all the traffic is going by only one network device. > > > > > > This is the configuration in my sys-usb: > > > > > > > > > > > > [user@sys-usb ~]$ ip route list > > > > > > default via 172.20.1.1 dev enp0s0u2 proto static metric 100 > > > > > > default via 192.168.8.1 dev enp0s0u3 proto static metric 101 > > > > > > 10.137.4.8 dev vif2.0 scope link metric 32750 > > > > > > 10.137.4.29 dev vif9.0 scope link metric 32743 > > > > > > 172.20.0.0/21 dev enp0s0u2 proto kernel scope link src > > > > > > 172.20.2.255 metric 100 > > > > > > 192.168.8.0/24 dev enp0s0u3 proto kernel scope link src > > > > > > 192.168.8.100 metric 100 > > > > > > > > > > > > The firewall IPs are 10.137.4.8 and 10.137.4.29 > > > > > > > > > > > > I know how to route a traffic to an specific IP using "ip route > > > > > > add" to a determined device network, but How can I route the > > > > > > complete traffic from one firewall VM by one device network and the > > > > > > traffic from other firewall VM by the other device network? > > > > > > > > > > Source based-routing is tricky in Linux in general. You can search for > > > > > some guides on the internet. > > > > > > > > > > But alternatively, on Qubes R3.2, you can assign one of those USB > > > > > devices to different VM - some separate netvm, or even one of those > > > > > firewallvms directly (and do not attach this firewallvm to any netvm). > > > > > It may work slightly slower, but should be much easier. > > > > > > > > Thanks for your tip Marek, but I am having an error with the USB assign: > > > > > > > > The ethernet adapter in the sys-usb VM: > > > > [user@sys-usb ~]$ lsusb > > > > ... > > > > Bus 005 Device 002: ID 0b95:1790 ASIX Electronics Corp. AX88179 Gigabit > > > > Ethernet > > > > ... > > > > > > > > And when I try to assing them to the sys-net VM in dom0: > > > > [user@dom0 ~]$ qvm-usb > > > > sys-usb:4-6 06cb:1ac3 SYNAPTICS_Synaptics_Large_Touch_Screen > > > > sys-usb:5-2 0b95:1790 ASIX_Elec._Corp._AX88179_:9 > > > > sys-usb:4-9 8087:07dc 8087_07dc > > > > sys-usb:4-110bda:573c > > > > CN0Y2TKG7248741DA3RDA00_Integrated_Webcam_HD_200901010001 > > > > [user@dom0 ~]$ qvm-usb -a sys-net sys-usb:5-2 > > > > ERROR: Device attach failed: /usr/lib/qubes/usb-import: line 51: > > > > printf: write error: Invalid argument > > > > > > > > Any idea or a detailed reference about this functionality? > > > > > > Check kernel messages in sys-net. It looks like kernel driver rejects > > > this device for some reason. > > > > > > > This is the message in sys-net: > > [ 3116.501714] vhci_hcd: Failed attach request for unsupported USB speed: > > super-speed > > > > And I see this i
Re: [qubes-users] Routing network traffic in sys-usb using multiple devices
El jueves, 18 de agosto de 2016, 9:45:44 (UTC-6), Marek Marczykowski-Górecki escribió: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA256 > > On Thu, Aug 18, 2016 at 08:25:34AM -0700, Adrian Rocha wrote: > > El viernes, 12 de agosto de 2016, 2:34:52 (UTC-6), Marek > > Marczykowski-Górecki escribió: > > > -BEGIN PGP SIGNED MESSAGE- > > > Hash: SHA256 > > > > > > On Thu, Aug 11, 2016 at 11:07:54AM -0700, Adrian Rocha wrote: > > > > Hi, > > > > > > > > I have two network devices and one only USB controller, so both devices > > > > are in the same VM (sys-usb). I want to route some app-VMs by one > > > > network and the rest by the other network, for that I have created two > > > > firewall VMs but both are connected to the same network VMs because, as > > > > I commented, I can not divide the network devices in different VMs. > > > > By default all the traffic is going by only one network device. This is > > > > the configuration in my sys-usb: > > > > > > > > [user@sys-usb ~]$ ip route list > > > > default via 172.20.1.1 dev enp0s0u2 proto static metric 100 > > > > default via 192.168.8.1 dev enp0s0u3 proto static metric 101 > > > > 10.137.4.8 dev vif2.0 scope link metric 32750 > > > > 10.137.4.29 dev vif9.0 scope link metric 32743 > > > > 172.20.0.0/21 dev enp0s0u2 proto kernel scope link src 172.20.2.255 > > > > metric 100 > > > > 192.168.8.0/24 dev enp0s0u3 proto kernel scope link src > > > > 192.168.8.100 metric 100 > > > > > > > > The firewall IPs are 10.137.4.8 and 10.137.4.29 > > > > > > > > I know how to route a traffic to an specific IP using "ip route add" to > > > > a determined device network, but How can I route the complete traffic > > > > from one firewall VM by one device network and the traffic from other > > > > firewall VM by the other device network? > > > > > > Source based-routing is tricky in Linux in general. You can search for > > > some guides on the internet. > > > > > > But alternatively, on Qubes R3.2, you can assign one of those USB > > > devices to different VM - some separate netvm, or even one of those > > > firewallvms directly (and do not attach this firewallvm to any netvm). > > > It may work slightly slower, but should be much easier. > > > > Thanks for your tip Marek, but I am having an error with the USB assign: > > > > The ethernet adapter in the sys-usb VM: > > [user@sys-usb ~]$ lsusb > > ... > > Bus 005 Device 002: ID 0b95:1790 ASIX Electronics Corp. AX88179 Gigabit > > Ethernet > > ... > > > > And when I try to assing them to the sys-net VM in dom0: > > [user@dom0 ~]$ qvm-usb > > sys-usb:4-6 06cb:1ac3 SYNAPTICS_Synaptics_Large_Touch_Screen > > sys-usb:5-2 0b95:1790 ASIX_Elec._Corp._AX88179_:9 > > sys-usb:4-9 8087:07dc 8087_07dc > > sys-usb:4-110bda:573c > > CN0Y2TKG7248741DA3RDA00_Integrated_Webcam_HD_200901010001 > > [user@dom0 ~]$ qvm-usb -a sys-net sys-usb:5-2 > > ERROR: Device attach failed: /usr/lib/qubes/usb-import: line 51: printf: > > write error: Invalid argument > > > > Any idea or a detailed reference about this functionality? > > Check kernel messages in sys-net. It looks like kernel driver rejects > this device for some reason. > > - -- > 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 > > iQEcBAEBCAAGBQJXtdghAAoJENuP0xzK19csjmEH/RKN1Wo8EsllAJ0jUfHcp4AP > GtjhLUYdU+zM2b+h37CLqGCLJ98Eeh4J/CMTH4B7MD6Y5TbCsJNfSxlLYfduPC4Y > zQa/MCDQ09Rof/iipT6SSXX/vRG+NyO+ssMWZM2URjGO0/IXyf0+RM7BI8syPq/L > FoNXyJU36F8BNAcihQZIJ1pDwj1gfEz8JJUEhX1rQgSvjUm7mmdpV2DCF1fYZ/OS > LsIBGrz+Ugja7dcYhwcxz1VkpXwPvExI/JceiLvlNxILwRaBtaBPMbX23CmknvB8 > T31N1IgJSxUQDgcPEhgu8MpHFyHmR5XhCQZmAJ+eMimhDdv4faLTCr2NKvXCSlg= > =/uUW > -END PGP SIGNATURE- This is the message in sys-net: [ 3116.501714] vhci_hcd: Failed attach request for unsupported USB speed: super-speed And I see this in sys-usb: [ 3095.918081] usbip-host 5-2: stub up [ 3095.920893] usbip-host 5-2: recv a header, 0 [ 3096.023678] usbip-host 5-2: reset SuperSpeed USB device number 2 using xhci_hcd [ 3096.038562] usbip-host 5-2: device reset -- 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/77b825ce-54ed-4b2e-bf47-734c6b58cacc%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Routing network traffic in sys-usb using multiple devices
El viernes, 12 de agosto de 2016, 2:34:52 (UTC-6), Marek Marczykowski-Górecki escribió: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA256 > > On Thu, Aug 11, 2016 at 11:07:54AM -0700, Adrian Rocha wrote: > > Hi, > > > > I have two network devices and one only USB controller, so both devices are > > in the same VM (sys-usb). I want to route some app-VMs by one network and > > the rest by the other network, for that I have created two firewall VMs but > > both are connected to the same network VMs because, as I commented, I can > > not divide the network devices in different VMs. > > By default all the traffic is going by only one network device. This is the > > configuration in my sys-usb: > > > > [user@sys-usb ~]$ ip route list > > default via 172.20.1.1 dev enp0s0u2 proto static metric 100 > > default via 192.168.8.1 dev enp0s0u3 proto static metric 101 > > 10.137.4.8 dev vif2.0 scope link metric 32750 > > 10.137.4.29 dev vif9.0 scope link metric 32743 > > 172.20.0.0/21 dev enp0s0u2 proto kernel scope link src 172.20.2.255 > > metric 100 > > 192.168.8.0/24 dev enp0s0u3 proto kernel scope link src 192.168.8.100 > > metric 100 > > > > The firewall IPs are 10.137.4.8 and 10.137.4.29 > > > > I know how to route a traffic to an specific IP using "ip route add" to a > > determined device network, but How can I route the complete traffic from > > one firewall VM by one device network and the traffic from other firewall > > VM by the other device network? > > Source based-routing is tricky in Linux in general. You can search for > some guides on the internet. > > But alternatively, on Qubes R3.2, you can assign one of those USB > devices to different VM - some separate netvm, or even one of those > firewallvms directly (and do not attach this firewallvm to any netvm). > It may work slightly slower, but should be much easier. Thanks for your tip Marek, but I am having an error with the USB assign: The ethernet adapter in the sys-usb VM: [user@sys-usb ~]$ lsusb ... Bus 005 Device 002: ID 0b95:1790 ASIX Electronics Corp. AX88179 Gigabit Ethernet ... And when I try to assing them to the sys-net VM in dom0: [user@dom0 ~]$ qvm-usb sys-usb:4-6 06cb:1ac3 SYNAPTICS_Synaptics_Large_Touch_Screen sys-usb:5-2 0b95:1790 ASIX_Elec._Corp._AX88179_:9 sys-usb:4-9 8087:07dc 8087_07dc sys-usb:4-110bda:573c CN0Y2TKG7248741DA3RDA00_Integrated_Webcam_HD_200901010001 [user@dom0 ~]$ qvm-usb -a sys-net sys-usb:5-2 ERROR: Device attach failed: /usr/lib/qubes/usb-import: line 51: printf: write error: Invalid argument Any idea or a detailed reference about this functionality? > > - -- > 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 > > iQEcBAEBCAAGBQJXrYojAAoJENuP0xzK19csd1AH/0xLELbOxgJSEbwImKU7OrYM > JVLl1hqGNx1iAy/6BGiV3IK0/CawomzVtoUcLli20WxTSjMqrrkoet5bRxWmZdYb > LWg2eHAjbFSL4hi20Rg6VPeYcFSy3BQH42YpfQnU2xlPjSXCCAJHfIbRsQpNJ8i3 > HPXcHfr3Gb1LqljgHjW/wrHzqc7T4uu4wGu28bPwow1EcSuVX8Ag7NZBeeqC1eDa > TjUOcmRXuY6BB7ofp2qzJQQBPHSMHdGM7G7QEEdxx1xy9E3knfs2i1HWKf2haR2s > uVfrCqsSjaTaoHFD3QSNk7gM6M6J1Eku9LUA4xosbbvN+H++O1jPfzXw98eXbxE= > =nMKF > -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/9a28a599-886f-473a-8f3e-62e9dee836e4%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Routing network traffic in sys-usb using multiple devices
Hi, I have two network devices and one only USB controller, so both devices are in the same VM (sys-usb). I want to route some app-VMs by one network and the rest by the other network, for that I have created two firewall VMs but both are connected to the same network VMs because, as I commented, I can not divide the network devices in different VMs. By default all the traffic is going by only one network device. This is the configuration in my sys-usb: [user@sys-usb ~]$ ip route list default via 172.20.1.1 dev enp0s0u2 proto static metric 100 default via 192.168.8.1 dev enp0s0u3 proto static metric 101 10.137.4.8 dev vif2.0 scope link metric 32750 10.137.4.29 dev vif9.0 scope link metric 32743 172.20.0.0/21 dev enp0s0u2 proto kernel scope link src 172.20.2.255 metric 100 192.168.8.0/24 dev enp0s0u3 proto kernel scope link src 192.168.8.100 metric 100 The firewall IPs are 10.137.4.8 and 10.137.4.29 I know how to route a traffic to an specific IP using "ip route add" to a determined device network, but How can I route the complete traffic from one firewall VM by one device network and the traffic from other firewall VM by the other device network? Regards -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/f87a6ebc-f7a0-4e38-86db-c0e4a6b13209%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Install kde/plasma desktop in qubes 3.2rc2
El lunes, 1 de agosto de 2016, 4:08:35 (UTC-6), Andrew David Wong escribió: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA512 > > On 2016-07-31 17:53, Adrian Rocha wrote: > > El domingo, 31 de julio de 2016, 17:53:01 (UTC-6), Marek > > Marczykowski-Górecki escribió: On Sun, Jul 31, 2016 at 04:40:16PM -0700, > > Andrew David Wong wrote: > >>>> On 2016-07-31 15:38, Adrian Rocha wrote: > >>>>> Hello all, > >>>>> > >>>>> I installed 3.2rc2 from scratch and I can't choose the kde/plasma > >>>>> desktop not even as an optional software. > >>>> > >>>> This was announced with the release of R3.2-rc2: > >>>> > >>>> "Beginning with this release, we’ve officially switched from KDE to > >>>> Xfce4, which is now the new default desktop environment in dom0." > > > >> I remember this announcement, but, why don't maintain it in the ISO as > >> alternative? > > > > Joanna explains the reasons for that here: > > https://github.com/QubesOS/qubes-issues/issues/2119 It's a pitty. I'm not agree, It's just my point of view becouse Xfce lacks many of the funcionality of KDE, and I don't consider these bugs as critical in KDE/Plasma 5. But it's just my opinion. About the instalation from the repo, it was fine, I just have had to change the window theme as Marek described here: https://groups.google.com/forum/#!msg/qubes-users/Y_v1wcl05iM/choRg3TfCgAJ Thanks > > >>>> > >>>> https://www.qubes-os.org/news/2016/07/28/ > >>>> qubes-OS-3-2-rc2-has-been-released/ > >>>>> > >>>> How can I install this desktop in this new release? > >>>>> > >>>> > >>>> Even though KDE was removed from the ISO, you should still be able > >>>> to install it from the repos. We don't have documentation for this > >>>> yet, but if the command matches Xfce, it should be: > >>>> > >>>> $ sudo qubes-dom0-update @kde-desktop-qubes > > > >> Perfect, I'm installing. > > > >> Many thanks > > > > > > Yes, exactly. > > > > > > - -- > Andrew David Wong (Axon) > Community Manager, Qubes OS > https://www.qubes-os.org > -BEGIN PGP SIGNATURE- > > iQIcBAEBCgAGBQJXnx+bAAoJENtN07w5UDAwHIYP/1lz32ePxk/o8Puz8cOvMrrO > 6cnXfTCUy1EtCmfmzYOdAAC9vOFt3FAumtVHT+J84j89bu2WV9bWdQQ8+9sYSLV1 > 46Ctk7ES1/zS5azTKAmqv48W3w1j8GHzThDangDlvQMmGiO4i2HXVWaNvyD8BhFE > Tff27nY0d0ymmNVHqK5k7fNAR26in2xws1O63Gqcc5X4x4TbVs3VadqAlzMezU1M > G3r3Iwv4cwPCng9yiFghba8pUKr/kGR+iw4QJKOJZ9ul7ZNyNWMA1494KUCbVNxN > 1D50pqxVivHZCSba/V68zXWx8DgBRfuDx+pVnb9Z4yGI/OP+qs80R3oxFPXDCSyf > VgKRY4HDiNbXIxgxZbhcyNsnAj5IYOsKdbQUX6G3wSc/YBSVMMUGLont0ZscyFVE > 5IrmZVRH/gftA5QolQde+qq8rO1ckG+Z1fCL21n8aJmqaSyPTckVxTSkgYTwXCu9 > 19Ba2wC9bgJ6/S3D6NymmN54/jmjuD6MTGJQVC5dbwKvh94mVycQXR4m0Xq8Ntxd > SHkxw+QvvpLKwB1ZLZJuXj/lwD/G/aunJ9KS1xmERH6kX7/4dPpfKNWEe/UzEl+q > NC6Om1K2NCrV4kzHOSiCBi3tqAgHV/PCEJI/I6cYqDabOj6VqVFfh9V6WyncJ1ut > psheeJLPkGaps7qVvzU1 > =IdcO > -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/8509965c-8cc9-4ed9-b69f-a3baf0b750c0%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Install kde/plasma desktop in qubes 3.2rc2
El domingo, 31 de julio de 2016, 17:53:01 (UTC-6), Marek Marczykowski-Górecki escribió: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA256 > > On Sun, Jul 31, 2016 at 04:40:16PM -0700, Andrew David Wong wrote: > > On 2016-07-31 15:38, Adrian Rocha wrote: > > > Hello all, > > > > > > I installed 3.2rc2 from scratch and I can't choose the kde/plasma desktop > > > not even as an optional software. > > > > This was announced with the release of R3.2-rc2: > > > > "Beginning with this release, we’ve officially switched from KDE to Xfce4, > > which is now the new default desktop environment in dom0." I remember this announcement, but, why don't maintain it in the ISO as alternative? > > > > https://www.qubes-os.org/news/2016/07/28/qubes-OS-3-2-rc2-has-been-released/ > > > > > How can I install this desktop in this new release? > > > > > > > Even though KDE was removed from the ISO, you should still be able to > > install > > it from the repos. We don't have documentation for this yet, but if the > > command matches Xfce, it should be: > > > > $ sudo qubes-dom0-update @kde-desktop-qubes Perfect, I'm installing. Many thanks > > Yes, exactly. > > - -- > 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 > > iQEcBAEBCAAGBQJXno9WAAoJENuP0xzK19csi8UH/A6i8oGtJdTBd7C4f5QiHuER > qwUCnXWbrPduaTL9SM7PLvzcyVx4HmD+pHbH3f4dy/w/ftJEf0bFRo/x1PIevzlZ > zUTcwmFy7v8ToLiXwoeePRnNKOBV3GUuf+qRSVgNGn/dUv1ETmczGNvfODHG08wr > AzPszYKxxLMEuGwxe65o6k++xkeGk4X3h6iiuLBHAJ7Rwxb0X9DkNSfsDPGj6Rb/ > 9K1hMgD77QwptpLbApW9l1Kkuk4UAQbll0q7khiO9xaeT1KF73tb6Okv6gXueR8j > 3LDb02KN979KRtbb9EgQcEcLutoedOunXP2mgkDG2Xvq+TuRpE5YEsxmdLvwSIc= > =18xI > -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/65956c3c-bd7c-4fde-bd7b-a12355b2e1e9%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Install kde/plasma desktop in qubes 3.2rc2
Hello all, I installed 3.2rc2 from scratch and I can't choose the kde/plasma desktop not even as an optional software. How can I install this desktop in this new release? Best Regards -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/52669c85-3697-4132-ba94-19f4c58ace08%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: Qubes Screenshot Tool with imgurl auto upload available. [beta]
El martes, 5 de julio de 2016, 5:39:13 (UTC-6), Eva Star escribió: > > (Instead of "qubed-dom0-update is "qubes-dom0-update") > > thank you > > > As I understand, in some versions of bash, the "\n" don't works as > > expected. So, I propose to change "echo" by "printf". You just have to add > > a "\n" at the end. > > thanks. I will fix it. > > > 2) I have dom0 in spanish. So, my Pictures folder is /home/user/Imágenes/ > > instead of /home/user/Pictures/. But when I run the script, it is saving > > the pictures in "/home/user/Pictures/" instead of ".../Imágenes" > > To obtain the correct directory to save the file you can use this command: > > xdg-user-dir PICTURES > > /home/user/Imágenes > > > > is it portable way to get PICTURES directory on other unix based systems? xdg-user-dir is a freedesktop.org tool. As I know, it works on Linux, Solaris and BSD. In the case of dom0, is a Fedora Linux, so we haven't any problem here. The issue can be with the VMs that doesn't have this command. There have to think in another way for this cases. -- 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/a6cb9b3d-051e-4df9-af8c-0055773f3cf3%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: Qubes Screenshot Tool with imgurl auto upload available. [beta]
Many thanks Eva, I'm testing it. First at all, its a great idea and, I appreciate very much your work. I have two minor issues with the script: 1) [user@dom0 Imágenes]$ ./qvm-screenshot-tool.sh [FATAL] no "zenity" tool at dom0 installeted use: \n\nsudo qubed-dom0-update zenity command to add it first (Instead of "qubed-dom0-update is "qubes-dom0-update") As I understand, in some versions of bash, the "\n" don't works as expected. So, I propose to change "echo" by "printf". You just have to add a "\n" at the end. 2) I have dom0 in spanish. So, my Pictures folder is /home/user/Imágenes/ instead of /home/user/Pictures/. But when I run the script, it is saving the pictures in "/home/user/Pictures/" instead of ".../Imágenes" To obtain the correct directory to save the file you can use this command: xdg-user-dir PICTURES /home/user/Imágenes Best Regards! -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/118cc2b5-6de8-4eb2-979c-679d0c35e264%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.