[qubes-users] Anyone have any luck setting up KDE Connect or another Android-sync tool?

['Sudomain' via qubes-users]

I've been trying to connect my android device to an appVM without any luck. I'm 
sure it's a firewall issue, so I tried setting up port forwarding using these 
instructions: 
https://www.qubes-os.org/doc/firewall/#port-forwarding-to-a-qube-from-the-outside-world
Forgive me, but I'm not very familiar with iptables. I'm not sure what kind of 
rules I would have to setup to get this working. According to the KDE Connect 
wiki: "KDE Connect uses dynamic ports in the range 1714-1764 for UDP and TCP. 
So if you are behind a firewall, make sure to open this port range for both TCP 
and UDP. Otherwise, make sure your network is not blocking UDP broadcast 
packets." (source: 
[https://community.kde.org/KDEConnect#Troubleshooting)](https://community.kde.org/KDEConnect#Troubleshooting)
 I would greatly appreciate any help with getting this to work or a working 
alternative. 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/mxbgRExR-LpUTCc3jCfgVleMO2xUj4Xe0X5vVnJsGDxLaPAe-LKh-sa-A2uHm1F8-TW_LOrxkkq9XJCaOcAMK97rwfPIlisfS9JJZ4XNFIk%3D%40protonmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Re: Yubikey in challenge/response mode to unlock LUKS on boot

[__ __]

Is there only one line? Or one line per uuid? Can you provide the complete
Output?

Regards
the2nd

Am 24.10.2017 5:31 vorm. schrieb "Ron Qubed" :

On Sunday, October 22, 2017 at 6:56:55 AM UTC-6, the2nd wrote:
> Hello,
>
> sorry for the long delay. Didnt had time to answer.
>
> If some of you is willing to help with testing LUKS-on-LVM could you
please provide the output of the commands below?
>
> sudo su -
> . /usr/lib/dracut/modules.d/99base/dracut-lib.sh
> getarg rd.ykluks.uuid
>
> If you have not modified your grub config for the ykluks dracut module
yet use this getarg command:
> getarg rd.luks.uuid
...
> Thanks
> the2nd

getarg rd.ykluks.uuid outputs nothing for me. But then, I'm not using a
Yubikey.

getarg rd.luks.uuid outputs "luks-", where lsblk shows that partition
name to be a "crypt [SWAP]" on sda3 (sda1 being my /boot/efi/, and sda2
containing "crypt /".

Not sure if/how any of this helps, but there it is.

Ron


--
You received this message because you are subscribed to a topic in the
Google Groups "qubes-users" group.
To unsubscribe from this topic, visit https://groups.google.com/d/
topic/qubes-users/hB0XaquzBAg/unsubscribe.
To unsubscribe from this group and all its topics, 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/3fe76359-4792-4177-b6a6-014426c8024b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

-- 
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/CAA0%2BMPfRiEG5anVtVgN08Utcgu_Bmhqmrys5voAAn0t1a0U82Q%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Re: Yubikey in challenge/response mode to unlock LUKS on boot

[Ron Qubed]

On Sunday, October 22, 2017 at 6:56:55 AM UTC-6, the2nd wrote:
> Hello,
> 
> sorry for the long delay. Didnt had time to answer.
> 
> If some of you is willing to help with testing LUKS-on-LVM could you please 
> provide the output of the commands below?
> 
> sudo su -
> . /usr/lib/dracut/modules.d/99base/dracut-lib.sh
> getarg rd.ykluks.uuid
> 
> If you have not modified your grub config for the ykluks dracut module yet 
> use this getarg command:
> getarg rd.luks.uuid
...
> Thanks
> the2nd

getarg rd.ykluks.uuid outputs nothing for me. But then, I'm not using a Yubikey.

getarg rd.luks.uuid outputs "luks-", where lsblk shows that partition 
name to be a "crypt [SWAP]" on sda3 (sda1 being my /boot/efi/, and sda2 
containing "crypt /".

Not sure if/how any of this helps, but there it is.

Ron


-- 
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/3fe76359-4792-4177-b6a6-014426c8024b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: Keyboard and Mouse Pad not Working [Solved]

[Ray Joseph]

On Saturday, October 21, 2017 at 8:06:57 PM UTC-5, Ray Joseph wrote:
> On Wednesday, October 4, 2017 at 6:31:49 AM UTC-5, Ray Joseph wrote:
> > After rebooting tow more times, the keyboard and mousepad became functional.
> > 
> > Ray
> 
> I have continued experimenting and and ran into to losing the input devices 
> again.  A day or so later, the I/O would come back up, and they go away 
> again.  
> 
> As I am relatively new to Linux, I dumped the journal to file and pulled it 
> into Excel.  I tagged those sections where I had not I/O; filtered, color 
> coded, sorted.  I could not find a correlation between no I/O and journal 
> entries.  Is there another resource I should be looking at?
> 
> I have just found that the laptop time/date was off.  So I went into the BIOS 
> and set it to UTC.  When it booted up, I/O was available.  I have rebooted a 
> couple times and I/O has been available each time.  
> 
> I don't know if this is 'fixed'.  
> 
> When the I/O was not available, I took pictures of messages during the boot 
> process and transcribed them (partially):
> [FAILED]  Failed to start Load Kernel Modules.
> See 'systemctl status systemd-modules-load.service' for details.
> [   10.108174] systemctl[1]:  Failed to start Load Kernel Modules.
> OK
> OK...
> Starting Show Plymouth Boot Screen...
> Starting dracut initqueue hook...
> 11.851549] [drm:intel_dp_link_training-channel_equalization [i915]] *ERROR 
> 5.4 Gbp link rate without HBR2/TPS3 support
> 
> After reading the above error, I went back to the journal file and found that 
> 'failed' showed up often in the file when there was no I/O.  I will study 
> this further to see if I can get a better idea of what is happening.  
> 
> BTW, I web searched for the above error and found this error to have occurred 
> in fedora and ubuntu; but those were consistent - they were not intermittent. 
>  I never found whether there was a related I/O failure.
> 
> If anything changes, I will report it back here.
> 
> Ray



I compared the output of the screen after a keyboard/touchpad failure and a 
successful boot.  The FAILURE lines are still there:
 [FAILED]  Failed to start Load Kernel Modules.
 See 'systemctl status systemd-modules-load.service' for details.
 [   10.108174] systemctl[1]:  Failed to start Load Kernel Modules.

The 'OK' lines were still there.

The last three lines were missing:
  Starting Show Plymouth Boot Screen...
  Starting dracut initqueue hook...
  11.851549] [drm:intel_dp_link_training-channel_equalization [i915]] *ERROR 
 5.4 Gbp link rate without HBR2/TPS3 support

Ray

-- 
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/f72ba143-abb1-4fa3-bf61-9e931a5a7178%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Safe Modifications Method for netvm

[Ray Joseph]

I would like to assure that I have a safe way to modify netvm.  I want to test 
configuring of a eth port and a wireless port.  

I would like to have a copy of the original, and keep copies of my test vms and 
possibly keep two (one wired one wireless) for normal use.

I don't know how to copy a vm none the less a safe method to develop 
modifications, versions and release versions.

I would like to understand how to carry out these type of tasks in qubes.

Thanks,
Ray

-- 
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/22f72f43-f518-4060-9d04-d691908cd18b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Unsolicited feedback on fedora 26 templates in Qubes R3.2

[Marek Marczykowski-Górecki]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

On Mon, Oct 23, 2017 at 10:11:07AM +0200, Alex wrote:
> On 10/20/2017 08:56 AM, Alex wrote:
> > Hi everybody,
> > I happened to notice that the RPMs needed to upgrade the qubes tools
> > inside templates to fc26 have appeared, and started my usual
> > clone-upgrade process to test the viability of the new major version.
> > 
> > So far I don't have any problems with the manually-upgraded fc26
> > templates (sudo dnf upgrade --releasever=26), the following software
> > tools work just as before:
> >  * firefox
> >  * thunderbird
> >  * urxvt
> >  * monodevelop (from flatpak packages)
> >  * android studio
> >  * the usual gnome file manager
> > 
> > And I did not have any problems with the UI tools interacting in any
> > weird way. So smooth.
> > 
> > Only thing I noticed is that now font settings seem to have changed - I
> > had set Bitstream Vera Sans as the default font in gnome-tweak-tool and
> > now I find Cantarell, and fonts in urxvt now are aliased and to fix that
> > I had to enable "Xft.antialias: true" in my .Xdefaults.
> > 
> > I still have to check the customized template for dispVM where I
> > compiled the samsung printer drivers, but I don't expect any major
> > problem there either.
> Updating the unsolicited feedback with more information; I found that
> other people have had troubles with fonts and upgrading fc25 -> fc26
> (i.e.
> https://utcc.utoronto.ca/~cks/space/blog/linux/Fedora26FontDilemma), and
> I'm working to understand what happened to my configurations.
> 
> I checked that the customized template with Samsung Printer Drivers do
> indeed work and print, and also LibreOffice and Pinta work just as usual
> - albeit with the messed up font rendering.

Thanks for the feedback!
I also noticed fonts difference, but haven't investigated it yet.

- -- 
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

iQEcBAEBCAAGBQJZ7jdPAAoJENuP0xzK19csYeEH/1Wnoa0CsZ1BCxNP4Bn0w4C8
nWztEYsXheWvTrBVRoi8JNfzrn0+gHz1Da3EZivmjkuz3c0/oCPNO+bzWtLLdMMr
XddFWGqWDiqgEaHfUNMEo2jWWV4xxQnTTrQ809EVPXcKcZ8sB1dTDw7eAT9IZ8Pa
eYN/OCs6XjFkwGcXDhIiBkqidfxGOigevtQhZmszOajQ/7oGOxmlA8ib/PpniJ+s
oZbzKjbC1LAg34ARjKfrIwPvAAB1JeJlJkYJltvpinfATkGlpsJrPJwDRCjGwd5m
T1bZMnoDR578NoAKBrFpj7xbk7qzWXPSCq1+CGMAAX6VYtStEZRUQCQIT9FCWos=
=j2Gn
-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/20171024005026.GA12669%40mail-itl.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: Update to Qubes 4rc2 Release Schedule

[samuel . jammeh]

On Tuesday, October 24, 2017 at 1:09:42 AM UTC+2, [799] wrote:
> Hello Qubes Dev's,
> 
> will there be an update to the release date of Qubes 4.0-rc2?
> I've looked at the website, but the release date is still the old one 
> (23.10/today)
> :
> https://www.qubes-os.org/doc/releases/4.0/schedule/
> 
> Don't want to put any pressure here, as I'd rather see open topics removed in 
> rc2 and what some days/week instead of having problems with the new release.
> 
> [799] 
> 
> 
> 
> 
> 
> Gesendet von ProtonMail mobile

its out, check out: https://ftp.qubes-os.org/iso/

-- 
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/b19e57c3-da70-45a6-aba6-0953fb4b0b27%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Re: XEN)QUBES END POINT SECYRITY

[Sven Semmler]

On 10/19/2017 03:52 PM, yuraei...@gmail.com wrote:
> If so, you can simply make good use of your AppVM firewall. For 
> example create a AppVM strictly and only for payments, then limit
> all internet connections in the firewall to only talk with your
> bank, and whichever additional services your bank may use. Although
> it can be a bit of a hassle with some services, who use many
> different domains, and they typically change too from time to time.
> Either way, this way, nothing gets into your bank AppVM, except
> those connections you allowed in.

That was my initial setup. I had a banking VM, a shopping VM and a
"untrusted web" VM. First I got rid of the "untrusted web" VM in favor
of just doing all non-logged-in browsing in a disposable VM.

Soon I realized that keeping the firewall configuration of the
shopping VM working was a constant battle ... so I got rid of it too.
Instead I am using a disposable VM instance, the additional step of
logging in isn't that painful (KeepassX in the vault VM and Qubes
Copy support).

Finally I didn't see the point in a dedicated banking VM anymore and
started using a disposable VM for that too.

Looking at my domains now, I have only one that is online and with
firewall rules (email). All others are offline (dev, office, vault).
All web browsing happens in a disposable VM.

I am pretty happy with that and are under the impression that this is
probably the safest I can get. Obviously this is only safe /
compartmentalized if one opens a new disposable VM for each
destination, which is reasonably fast on my machine.

/Sven

-- 
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/829b68d4-5720-0175-0944-42ebe481e5c7%40SvenSemmler.org.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Update to Qubes 4rc2 Release Schedule

['[799]' via qubes-users]

Hello Qubes Dev's,

will there be an update to the release date of Qubes 4.0-rc2?
I've looked at the website, but the release date is still the old one 
(23.10/today)
:
https://www.qubes-os.org/doc/releases/4.0/schedule/

Don't want to put any pressure here, as I'd rather see open topics removed in 
rc2 and what some days/week instead of having problems with the new release.

[799]

Gesendet von ProtonMail mobile

-- 
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/z24iiaUj6B-mJxzrnpfjkDevasJEJ9_oO8--6-vwZSDMdiNd3_79fZlx4C64kg1-xQtKMHBeX3Rs9h93uaB-uy4BJjUpX5_dwb1ojyyqMzo%3D%40protonmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Re: cannot trim whonix-ws template anymore

[Sven Semmler]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

On 10/20/2017 10:25 AM, Noor Christensen wrote:
> $ virsh undefine 34bfb7d4-b96d-4d8d-9042-53e212761316

Thank you Noor!

The above command did the trick.

/Sven


-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQIcBAEBCAAGBQJZ7nGUAAoJENpuFnuPVB+2Oo4QAKFSqV6D3viMZccDjq13qsVw
yuggf4mUfyRZX1s2M8L2R0TOn6Z4eof8X9z1Zfj/dKfcWXJFdbLOwhKmHTXS+i2X
cPgCWdHuXg2RoPe77GKjp1buJ0YlbLvpUxPEcAVScOwCET/0shZ02UF0Cr7imsHl
jvNZdB4kd4VS3O0s21ED/L8upAUsen5Fn3P09om0lMMasrRMOrpBOeJ/wYQbBJA9
7klPpcbgli+zh1hAPcnRpu8tQU777pbbbkmMgaSxSNFUmXsjh3SDHQO/kS4ol+Cz
eGRsNLuZ7eohr0p3ObO1EXgW2c7E3+YEZs/uSwhGSFPwB3SMzprhWO2z+6ZBiUgY
Komd6FK7WrcOoDEEe4hjowGBnxmhtK8Wg8MMfpKPtIMck7f3GhE8vHMBVyP6YMVi
pK5u6uw0a0j2nM4fu4g3X+Yh2T8C0G/Zfk7BktLRMhf7UikHxb0GD8MvYJBGmPib
RKj86B1rpRdngFOApbxynJRA8MRqTTULxRzx3yA3ByCtZrADOmnBH7gv1lVOavCI
hQzzP/J4dIOfaLTyLT/Z3dGA0Ue/nGNHoNGHhDpCuVCGWBukGn6eht8bK/xmtfz5
NwbrqdRQnebA9NgGH4VqjIw7TscMjL1Y31I5o1BncrjJ8hYVQLOjdeWApKaurtLs
tmslBaZc235FL6lKAA3A
=wVtg
-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/5e67dc9b-b31f-bf06-467f-cae757aee71e%40SvenSemmler.org.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: Support for Windows Tools (QWT) for Qubes 4.0 RC1

[Foppe de Haan]

On Monday, October 23, 2017 at 7:43:35 PM UTC+2, olesiaka...@gmail.com wrote:
> On Monday, October 23, 2017 at 1:28:59 PM UTC-4, joev...@gmail.com wrote:
> > On Monday, 23 October 2017 11:37:13 UTC-4, Olesia K  wrote:
> > > hello Qubes users
> > > 
> > > I am trying to get windows tools installed on Qubes4.0 RC1. I a getting 
> > > an error message when I do so.
> > > 
> > > Input:
> > > sudo qubes-dom0-update --enablerepo=qubes-dom0-current-testing 
> > > qubes-windows-tools
> > > 
> > > Result:
> > > Failed to synchronize cache for repo 'qubes-dom0-unstable', disabling. 
> > > Last metdata expiration check:0:00:05 ago on Mon Oct 23 07:35:40 2017. No 
> > > package qubes-windows-tools available. 
> > > Error: Unable to find match.
> > 
> > Are your sys-firewall and sys-net VMs running?
> > When you run qubes-dom0-update, it sends commands to the firewall via 
> > qrexec to allow dom0 outbound to the update servers.
> 
> Yes. I have both sys-net and sys-firewall running.

QWT hasn't been built for r4.0 yet, so you can't install it yet.

-- 
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/7e2d6e56-3486-4f31-bc51-c4917b47%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: Support for Windows Tools (QWT) for Qubes 4.0 RC1

[olesiakazantseva]

On Monday, October 23, 2017 at 1:28:59 PM UTC-4, joev...@gmail.com wrote:
> On Monday, 23 October 2017 11:37:13 UTC-4, Olesia K  wrote:
> > hello Qubes users
> > 
> > I am trying to get windows tools installed on Qubes4.0 RC1. I a getting an 
> > error message when I do so.
> > 
> > Input:
> > sudo qubes-dom0-update --enablerepo=qubes-dom0-current-testing 
> > qubes-windows-tools
> > 
> > Result:
> > Failed to synchronize cache for repo 'qubes-dom0-unstable', disabling. Last 
> > metdata expiration check:0:00:05 ago on Mon Oct 23 07:35:40 2017. No 
> > package qubes-windows-tools available. 
> > Error: Unable to find match.
> 
> Are your sys-firewall and sys-net VMs running?
> When you run qubes-dom0-update, it sends commands to the firewall via qrexec 
> to allow dom0 outbound to the update servers.

-- 
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/fa9f4fce-abec-4a09-98bb-8cdec1e20784%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: Support for Windows Tools (QWT) for Qubes 4.0 RC1

[olesiakazantseva]

On Monday, October 23, 2017 at 1:28:59 PM UTC-4, joev...@gmail.com wrote:
> On Monday, 23 October 2017 11:37:13 UTC-4, Olesia K  wrote:
> > hello Qubes users
> > 
> > I am trying to get windows tools installed on Qubes4.0 RC1. I a getting an 
> > error message when I do so.
> > 
> > Input:
> > sudo qubes-dom0-update --enablerepo=qubes-dom0-current-testing 
> > qubes-windows-tools
> > 
> > Result:
> > Failed to synchronize cache for repo 'qubes-dom0-unstable', disabling. Last 
> > metdata expiration check:0:00:05 ago on Mon Oct 23 07:35:40 2017. No 
> > package qubes-windows-tools available. 
> > Error: Unable to find match.
> 
> Are your sys-firewall and sys-net VMs running?
> When you run qubes-dom0-update, it sends commands to the firewall via qrexec 
> to allow dom0 outbound to the update servers.

Yes. I have both sys-net and sys-firewall running. 

-- 
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/e87a899f-0210-4c92-82ca-dae3893e74af%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: Support for Windows Tools (QWT) for Qubes 4.0 RC1

[joeviocoe]

On Monday, 23 October 2017 11:37:13 UTC-4, Olesia K  wrote:
> hello Qubes users
> 
> I am trying to get windows tools installed on Qubes4.0 RC1. I a getting an 
> error message when I do so.
> 
> Input:
> sudo qubes-dom0-update --enablerepo=qubes-dom0-current-testing 
> qubes-windows-tools
> 
> Result:
> Failed to synchronize cache for repo 'qubes-dom0-unstable', disabling. Last 
> metdata expiration check:0:00:05 ago on Mon Oct 23 07:35:40 2017. No package 
> qubes-windows-tools available. 
> Error: Unable to find match.

Are your sys-firewall and sys-net VMs running?
When you run qubes-dom0-update, it sends commands to the firewall via qrexec to 
allow dom0 outbound to the update servers.

-- 
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/badeccf3-b9ad-4355-a2dc-c433a1d2365d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Support for Windows Tools (QWT) for Qubes 4.0 RC1

[Olesia K]

hello Qubes users

I am trying to get windows tools installed on Qubes4.0 RC1. I a getting an
error message when I do so.

*Input:*
sudo qubes-dom0-update --enablerepo=qubes-dom0-current-testing
qubes-windows-tools

*Result:*
Failed to synchronize cache for repo 'qubes-dom0-unstable', disabling. Last
metdata expiration check:0:00:05 ago on Mon Oct 23 07:35:40 2017. No
package qubes-windows-tools available.
Error: Unable to find match.

-- 
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/CAC5mC2Aks4-KfoyWxxL37PO%2Bfjg8zEGqcRjDBKBVi0Dopnw%3DcQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: Qubes 4.0-rc2 release

[platagregor]

Am Montag, 16. Oktober 2017 20:17:02 UTC+2 schrieb Foppe de Haan:
> On Monday, October 16, 2017 at 8:07:37 PM UTC+2, plata...@gmail.com wrote:
> > Dear Qubes Team,
> > 
> > in there the next delay or will the 4.0-rc2 be released in the next couple 
> > of hours (today)?
> > 
> > regards
> > 
> > gregor
> 
> Delayed one week. Reasons here: 
> https://groups.google.com/forum/#!topic/qubes-devel/23FwvVd-pjU

Delayed again or is there still a chance for 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/4f1de0ec-e362-4ec5-bab1-bd124beb7225%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Re: External monitor not getting highest resolution

[Markus Kilås]

On 09/27/2017 11:11 AM, Markus Kilås wrote:
> On 09/22/2017 09:38 AM, Markus Kilås wrote:
>> On 09/20/2017 10:16 PM, yuraei...@gmail.com wrote:
>>> On Wednesday, September 20, 2017 at 3:16:59 PM UTC, Markus Kilås wrote:
 On 09/08/2017 06:17 AM, Pagebao wrote:
> Same thing is happening to me since the last Dom0 update. My ultrawide 
> 29" LG external screen stopped working at the native 2560x1080 resolution 
> and instead is working at 1920x1080.

 Oh, that is interesting to know. I did not know this was a regression as
 I did not use external monitor before.

>
> I have a Lenovo Thinkpad T430s. I was using nouveau driver but the same 
> thing is happening with the integrated Intel graphic card.
>
> Fortunately I had a full backup from August 9 so, reinstalling Qubes 3.2 
> and  restoring Dom0 and all the VM the problem is, temporarily, fixed and 
> I have back 2560x1080 resolution.
>
> But the most maddening thing is that I tried several different distro 
> (Linux Mint 18.2, MX 16.0, Manjaro) and I have the same problem. Only 
> 1920x1080px. In the previous 1.5 years I had no problem of resolution 
> with Qubes 3.2 and Linux Mint 18.1.
>

 So it could be more of generic Linux issue then? Some problem with
 certain kernel or nouveau versions perhaps?

> Tried cvt and xrandr --newmode and --addmode to no avail so far (no 
> effect on Qubes, screen blanked on Linux Mint).
>
> Again, any idea?>
> Thanks
>

 Anything else one can try to resolve this?

 Cheers,
 Markus
>>>
>>> Did you try going back to the previous kernel? The 4.9.35-20? or even the 
>>> 4.4'ish version if its still in your system?> Also it may not be relevant 
>>> as my problem with the new kernel
>> (4.9.45-21) is of a seemingly very different nature (didn't boot due to
>> wanting root account, whatever odd bug was causing that error). Albeit I
>> never made it as far to see whether I lost my resolution as well while
>> running the new kernel.
>>
>> I believe I was on 4.9.35-20 and had the issue but will double check.
>>
>>>
>>> Assuming you haven't gone back to older kernels before, it's easy to do 
>>> without uninstalling/installing anything. If you got Grub2 (Legacy Qubes 
>>> install mode), then just change to the old kernel during early boot in 
>>> Grub2's advance menu. If you boot up with UEFI/EFI then you need to change 
>>> the default boot kernel in the /boot/efi/Qubes/xen.conf (somewhere there 
>>> abouts. Be careful though, wrong settings will make your system unable to 
>>> boot up).
>>>
>>> Obviously far easier to quickly change with Grub2, but it isn't much of a 
>>> hassle either with editing the xen.cong file if you boot via the modern 
>>> UEFI instead. Just be careful with the settings.
>>
>> Thank you, this instructions are very helpful.
>>
>>
>> I am using Grub2 and legacy boot so will try the different kernels on
>> Tuesday when I am back in office and have access to the monitor.
>>
>>
>>>
>>> Also if it may be of any help, I run Qubes with 3840x2160, 4k resolution 
>>> with kernel 4.9.35-20, nvidia/integrated Intel-M processor graphics, and 
>>> XFCE4 as my DE. As mentioned earlier, I'm holding back on the current new 
>>> Dom0 update with the 4.9.45-21, since it gives me boot issues. Furthermore, 
>>> I have a lot of issues getting my HDMI TV back on my laptop after 
>>> suspend/hibernation on my current older kernel. Also if I unplug the HDMI, 
>>> etc. usually I need to go into "xfce4-display" and turn on the screen 
>>> manually. Maybe its related to some of the black screen mentioned issues, 
>>> albeit it might be different too.
>>>
>>> I'm afraid I can't try help with anything deeper if the problem still 
>>> persists. Remember to make backups before experimenting with solutions 
>>> though, it's such a pain to loose things...
>>>
>>> If kernels are a suspect, we should list our kernels in case we can find 
>>> clues. Try throw "uname -r" in your Dom0 terminal to list it.
>>>
>>
>> Currently I have uname -a:
>> Linux dom0 4.9.45-21.pvops.qubes.x86_64 #1 SMP Tue Aug 29 14:21:02 UTC
>> 2017 x86_64 x86_64 x86_64 GNU/Linux
>>
>> I will retry 4.9.45-20 and also try the oldest I have which is 4.9.35-19.
> 
> I have the issue with all three available kernels:
> 4.9.45-21
> 4.9.35-20
> 4.9.35-19
> 
> Is there a way to install older kernels?
> 
> I tried "sudo qubes-dom0-update --action=list kernel-qubes-vm" but those
> are the only available.
> 

After one of the last updates, the external monitor is working again on
high resolution. It was not a kernel update that solved it as I am still
on 4.9.45-21.

Regards,
Markus


-- 
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 

Re: [qubes-users] Re: External monitor not getting highest resolution

[Markus Kilås]

On 09/27/2017 11:11 AM, Markus Kilås wrote:
> On 09/22/2017 09:38 AM, Markus Kilås wrote:
>> On 09/20/2017 10:16 PM, yuraei...@gmail.com wrote:
>>> On Wednesday, September 20, 2017 at 3:16:59 PM UTC, Markus Kilås wrote:
 On 09/08/2017 06:17 AM, Pagebao wrote:
> Same thing is happening to me since the last Dom0 update. My ultrawide 
> 29" LG external screen stopped working at the native 2560x1080 resolution 
> and instead is working at 1920x1080.

 Oh, that is interesting to know. I did not know this was a regression as
 I did not use external monitor before.

>
> I have a Lenovo Thinkpad T430s. I was using nouveau driver but the same 
> thing is happening with the integrated Intel graphic card.
>
> Fortunately I had a full backup from August 9 so, reinstalling Qubes 3.2 
> and  restoring Dom0 and all the VM the problem is, temporarily, fixed and 
> I have back 2560x1080 resolution.
>
> But the most maddening thing is that I tried several different distro 
> (Linux Mint 18.2, MX 16.0, Manjaro) and I have the same problem. Only 
> 1920x1080px. In the previous 1.5 years I had no problem of resolution 
> with Qubes 3.2 and Linux Mint 18.1.
>

 So it could be more of generic Linux issue then? Some problem with
 certain kernel or nouveau versions perhaps?

> Tried cvt and xrandr --newmode and --addmode to no avail so far (no 
> effect on Qubes, screen blanked on Linux Mint).
>
> Again, any idea?>
> Thanks
>

 Anything else one can try to resolve this?

 Cheers,
 Markus
>>>
>>> Did you try going back to the previous kernel? The 4.9.35-20? or even the 
>>> 4.4'ish version if its still in your system?> Also it may not be relevant 
>>> as my problem with the new kernel
>> (4.9.45-21) is of a seemingly very different nature (didn't boot due to
>> wanting root account, whatever odd bug was causing that error). Albeit I
>> never made it as far to see whether I lost my resolution as well while
>> running the new kernel.
>>
>> I believe I was on 4.9.35-20 and had the issue but will double check.
>>
>>>
>>> Assuming you haven't gone back to older kernels before, it's easy to do 
>>> without uninstalling/installing anything. If you got Grub2 (Legacy Qubes 
>>> install mode), then just change to the old kernel during early boot in 
>>> Grub2's advance menu. If you boot up with UEFI/EFI then you need to change 
>>> the default boot kernel in the /boot/efi/Qubes/xen.conf (somewhere there 
>>> abouts. Be careful though, wrong settings will make your system unable to 
>>> boot up).
>>>
>>> Obviously far easier to quickly change with Grub2, but it isn't much of a 
>>> hassle either with editing the xen.cong file if you boot via the modern 
>>> UEFI instead. Just be careful with the settings.
>>
>> Thank you, this instructions are very helpful.
>>
>>
>> I am using Grub2 and legacy boot so will try the different kernels on
>> Tuesday when I am back in office and have access to the monitor.
>>
>>
>>>
>>> Also if it may be of any help, I run Qubes with 3840x2160, 4k resolution 
>>> with kernel 4.9.35-20, nvidia/integrated Intel-M processor graphics, and 
>>> XFCE4 as my DE. As mentioned earlier, I'm holding back on the current new 
>>> Dom0 update with the 4.9.45-21, since it gives me boot issues. Furthermore, 
>>> I have a lot of issues getting my HDMI TV back on my laptop after 
>>> suspend/hibernation on my current older kernel. Also if I unplug the HDMI, 
>>> etc. usually I need to go into "xfce4-display" and turn on the screen 
>>> manually. Maybe its related to some of the black screen mentioned issues, 
>>> albeit it might be different too.
>>>
>>> I'm afraid I can't try help with anything deeper if the problem still 
>>> persists. Remember to make backups before experimenting with solutions 
>>> though, it's such a pain to loose things...
>>>
>>> If kernels are a suspect, we should list our kernels in case we can find 
>>> clues. Try throw "uname -r" in your Dom0 terminal to list it.
>>>
>>
>> Currently I have uname -a:
>> Linux dom0 4.9.45-21.pvops.qubes.x86_64 #1 SMP Tue Aug 29 14:21:02 UTC
>> 2017 x86_64 x86_64 x86_64 GNU/Linux
>>
>> I will retry 4.9.45-20 and also try the oldest I have which is 4.9.35-19.
> 
> I have the issue with all three available kernels:
> 4.9.45-21
> 4.9.35-20
> 4.9.35-19
> 
> Is there a way to install older kernels?
> 
> I tried "sudo qubes-dom0-update --action=list kernel-qubes-vm" but those
> are the only available.
> 
> 
> Regards,
> Markus
> 

Since one of the last updates, high resolution on external monitor is
working. I am still on 4.9.45-21 so it was not a kernel change that
solved it.


Regards,
Markus

-- 
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 

Re: [qubes-users] Unsolicited feedback on fedora 26 templates in Qubes R3.2

[Alex]

On 10/20/2017 08:56 AM, Alex wrote:
> Hi everybody,
> I happened to notice that the RPMs needed to upgrade the qubes tools
> inside templates to fc26 have appeared, and started my usual
> clone-upgrade process to test the viability of the new major version.
> 
> So far I don't have any problems with the manually-upgraded fc26
> templates (sudo dnf upgrade --releasever=26), the following software
> tools work just as before:
>  * firefox
>  * thunderbird
>  * urxvt
>  * monodevelop (from flatpak packages)
>  * android studio
>  * the usual gnome file manager
> 
> And I did not have any problems with the UI tools interacting in any
> weird way. So smooth.
> 
> Only thing I noticed is that now font settings seem to have changed - I
> had set Bitstream Vera Sans as the default font in gnome-tweak-tool and
> now I find Cantarell, and fonts in urxvt now are aliased and to fix that
> I had to enable "Xft.antialias: true" in my .Xdefaults.
> 
> I still have to check the customized template for dispVM where I
> compiled the samsung printer drivers, but I don't expect any major
> problem there either.
Updating the unsolicited feedback with more information; I found that
other people have had troubles with fonts and upgrading fc25 -> fc26
(i.e.
https://utcc.utoronto.ca/~cks/space/blog/linux/Fedora26FontDilemma), and
I'm working to understand what happened to my configurations.

I checked that the customized template with Samsung Printer Drivers do
indeed work and print, and also LibreOffice and Pinta work just as usual
- albeit with the messed up font rendering.

-- 
Alex

-- 
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/ffd82978-5bb1-2d8b-4037-b427164a7482%40gmx.com.
For more options, visit https://groups.google.com/d/optout.


signature.asc
Description: OpenPGP digital signature

Re: [qubes-users] Re: qubes 4.0 RC1 networking problems

[Sean Hunter]

Fedora works just fine for me as the template for sys-net in 4rc1 here.

As a first step what I would do is if sys-net can get online, set sys-net as 
updatevm for dom0, apply all the dom0 updates, then open a terminal in whatever 
you’re using as template for sys-net and apply all updates there (first set 
sys-net as updatevm there too).  Then shutdown that template vm and restart 
sys-net and sys-firewall so they get the updates. 

Once that’s working remember to set the updatevms back to sys-firewall. 

Sean

Sent from my phone. Sorry if brief. 

> On 22 Oct 2017, at 23:15, Francesco Rmp  wrote:
> 
> Il giorno domenica 22 ottobre 2017 16:29:14 UTC-4, yura...@gmail.com ha 
> scritto:
>> On Sunday, October 22, 2017 at 5:27:17 PM UTC, Francesco Rmp wrote:
>>> Hello everyone,
>>> i've just installed qubes 4.0 RC1 on my ryzen system ( i couldn't get the 
>>> 3.2 to install because of the kernel compatibility).
>>> 
>>> The installation went smooth and i can boot fine in the system, but i'm 
>>> having some networking issues.
>>> 
>>> Making the long story short: i cant get any VM to go online.
>>> 
>>> I'm no that familiar with the networking in qubes, but i tried to do some 
>>> troubleshooting myself, and here is what i get.
>>> 
>>> - The sys-net VM works fine, it gets the IP from DHCP, gateway, DNS and 
>>> everything and this is the only VM that goes online. i can ping hosts and 
>>> communicate with the network. I didn't do anything fency in this VM but 
>>> using some terminal commads to check i could actually go online, and it 
>>> works.
>>> 
>>> This network fetches the IPs from my DHCP and is set to a 192.168.1.0/24
>>> 
>>> - the sys-firewall VM doesn't go online at all. I checked the VM 
>>> configuration in qubes manager, and according to the configuration, it 
>>> looks like it's using sys-net as its gateway, but still nothing.
>>> Curious that when i check in the terminal, it has a network interface with 
>>> class 10.xxx (i dont' remember exactly) and an additional interface for 
>>> each appVM that i spin up (this is fine).
>>> My question is.. how can this VM masquarade any traffic to the sys-net VM 
>>> if the class of the network interface is completely different and the 
>>> gateway is actually not set to the sys-net VM ip?
>>> 
>>> - As a consequence of the fact that the sys-firewall VM doesn't go online, 
>>> all the appVMs suffer the same problem.
>>> 
>>> Can anyone help me out in troubleshooting this problem?
>>> Am i right to assume that this is not an hardware problem? considering that 
>>> the physical network interface assigned to sys-net works fine?
>>> 
>>> thanks in advance for your kind reply and support.
>> 
>> 
>> Typically the Firewall AppVM is not happy to go online if there are problems 
>> with the sys-net AppVM. The issue is therefore likely in the sys-net AppVM, 
>> and not the firewall AppVM. For example if you take a fully functioning 
>> Qubes system, and you kill off the sys-net AppVM, while allowing the 
>> firewall AppVM to stay online, and then start up sys-net again, will cause 
>> issues with the Firewall AppVM. You'll have to shutdown the firewall AppVM 
>> and start it again, to establish a proper tied connection with the sys-net. 
>> Something similar is likely happening here, if there is something not 
>> properly working in your sys-net.
>> 
>> There are likely two reasons to the problems you face, that I can think of.
>> 
>> - The first issue is the planned premature release of Qubes 4 (kind of alpha 
>> release), does not always support PCI passthourgh too well, which might 
>> explain why your network card can't be passed through properly. Indeed it 
>> might work for a single VM, but if it can't communicate perfectly, it might 
>> cause the Firewall AppVM to bug out (A possibility). This major Qubes 4-RC1 
>> issue has very recently been fixed, as early as last week. But since you 
>> don't have networking, you can't fetch the patch that fixes it. You're in 
>> luck though, Qubes 4-RC2 is planned to be released tomorrow, as you can see 
>> here https://www.qubes-os.org/doc/releases/4.0/schedule/
>> It shouldn't be delayed once more, a major issue holding it back, is exactly 
>> the issue up above causing problems with PCI passthrough hardware in Qubes 
>> 4. If this still does not work,then you can try turn your Passthrough 
>> AppVM's into PV virtualization mode, instead of HVM mode, which Qubes 4 can 
>> do with a single command. I believe it should be in terminal dom0: QVM-prefs 
>> "AppVM name" -l
>> somewhere. I don't run Qubes 4 atm, so I can't check, but it should be easy 
>> to do, from what I've heard. 
>> 
>> - The other issue, that I can think of, is Ryzen. The kernel that almost 
>> fully supports Ryzen should be around version 9.12+. For example I've seen 
>> Qubes with Ryzen that only partially allow USB passthrough, but not fully 
>> passtrough, causing weird issues. Qubes does not run version 9.12 just yet 
>>