[qubes-users] Re: Re: Qubes User Forum

2018-11-09 Thread Sven Semmler
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Testing to post from the forum. First impressions:

- - Pretty sure I want to post from my mail client, since I
like my stuff
  to be signed. Faking an email address is way to easy.

- - Following a discussion might be faster in the mail
client too, but I
  can see that there are probably (younger?) folks who grew
up with
  forums. I still mourn the usenet.

- - If this POC gets legs, it would be very useful if the
software would
  become GPG/PGP aware (as in verifying signatures and
hiding the actual
  signatures)

/Sven
-BEGIN PGP SIGNATURE-

 iQIzBAEBCAAdFiEE18ry22WNibwI1qeq2m4We49UH7YFAlvmVQAACgkQ2m4W
e49U
 H7aSjRAAmGAGV7uz2WeKd0O41xwEgc/i3DtxkEH3+Z+L7udThxucyrb9UOKO
8igh
 GU9RahC3hEZB+ACJ/zX+3OHztLE3yMribdxJRlJGZuPFFczWj9eQL9lgkxX5
BZ/E
 EHozhlXyQdD93Z3B6mQm6lYxMt4Ssy22xFxDEVs/5RTPSeH8i0hmDIlwu4WL
armg
 e0gh4h87XURMEpahUK+mwoktyeTYBHoKm5Y9zbe2b6QXk4sh9p3j00R55Ne4
Movj
 MBJuITpYFSqFWDac1Wd2olme+XdDhSxqAs/9AFPZZCZIkU6CEHBIfVHeWIqU
J3Jw
 4Nt1ee+aCuAQqunti8YpmAqETDWbAxtwSQ8wJ/znQnAi8AiVhviIrzemqq/Q
FMda
 SEduBg+NFkhrGYX0UaeGxXJJ8tiv4MHl08YPJHLiEPDT83E8dAkmTzME7sAS
c2E/
 AnjYdsBRJrur94/7TCLU8bydrUc0YU9Hwq1fY7Tsq5OGSNC8Q4TZ/MUvoDWI
Knya
 smY2rWEo9Ksif1aXEmQ/5GUT2nCSM2A6oPZdgaDztBh8mhfOIZHkNrl1d4lG
YxoH
 jSYjJ6WA/cFM6MhZzgOWi6/0nj6T2pVogNVw2ce1FjeG+uujPKxW5SQt8CqW
nSxF
6CZrwiFXK43aQQMdSC8uVYQn24iLaQxIc2vFOmG7GNW+iLw5HEA=
=njLH
-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/1e8.5be6556b%40qubes-os.info.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] Costum qubes order in QVM

2018-11-09 Thread Sven Semmler
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

On 11/2/18 8:20 AM, pieter lems wrote:
> How does one costumize the order in wich the qubes are displayed.

If you want a solution without programming: use a naming convention. I
use simple prefix:

app-... for AppVMs
dvm-... for DispVM templates
sys-... for system qubes
sys-dvm-... for disposable system qubes
tpl-... for templates

Both qvm-ls and qubes-qube-manager will show your qubes somewhat
ordered that way.

/Sven
-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEE18ry22WNibwI1qeq2m4We49UH7YFAlvmSwQACgkQ2m4We49U
H7ZQAA/+JK4PHdoVFFmHYw0VDbQA6Gj2P4WeYtqUaxTdPeH8fdLon+fzmFxe6Wph
hS/18fvSL9hsX9/UE5L/G2JseedKKReqQheQhhRWsSurZw3+KiWIgi6l+KzSMv6u
5mSieodtLZus1LeplYCA0/fHQmNgdE1+ArNTcGNhJfOfHbuacmqdFeq2aaaSNL8q
2uPzpwu9wm/O5wcXBg06pNVHQJ5BVm1DBCvUSApONwT+GvdJu/GMz/YeZcPTuS/x
cB5b4TRkzlhCJJ1ytdStNU/EOgE3q7nXTDcZmlCjssJb3ouRxT0gCI/S5fyEgZmg
ufcGe80Y/e1ocqGbJwx1IY7EnrZg/y1jqcr+KrCHqoSDSs7SpLjbgN7jUeXgb6Hc
T73ndVxATbjFt28JZhv2EkiQdadqyl1N7G2a0DJaAY/WTfcgnEETQt9ev0PdY9xP
OPISKvQ8byxfazJoDL/DByV61PYQ4kCKxh1dOO3jTt/JyJM8TyK9+PQsGaoUNkTe
6NH5qeEP0pW8Sv1VTMPHMyD1no+t+1Y9VAXjYhs47Q4zWYcqhi6QAW6YZJuuOuLX
0i09++sz2ig6rPjSwLVkzU6576/3q7pJ3v001NiR783SYMEPC+txe+PQw22Fjvyf
jat+YsZ2D62Juk80ok9K0KzxV6G/z11MGEJSnHS8jqjvADt8h4I=
=+8Hd
-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/8d88df08-f7f6-e6c5-ed2d-dfcbb15d725a%40SvenSemmler.org.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] ERROR: Tor Bootstrap Result:

2018-11-09 Thread William Fisher
Turned out to be a clock settings problem. Set the clock to UTC and poof it 
works!

-- 
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/d96147d8-469b-4204-92cd-bafb7d4cd2e7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Fresh install Failed to synchronize cache for repo 'qubes-dom0-current' and 'qubes-templates-itl'

2018-11-09 Thread alrojs
Hardware: t460p and t450s
I am currently on my fourth install of qubes and using 4.0 rc1 build.

The operating system seems to work fine. I am able to create proxyvm's, and 
link them together  appvm>vpn1>vpn2>sys-whonix>sys-firewall>sys-net(main goal 
opsec). On my first and second install I was able to set up all these vm's, 
however when I wanted to update dom0 or install package u2f to use my yubikey I 
would always encounter this issue updating. 

whole output on terminal dom0
[user@dom0 ~] sudo qubes-dom0 update
using sys-firewall as UpdateVM to download updates for Dom0; this may take some 
time...
Qubes Dom0 Repository (updates)63 B/s | 169 B  00:02
Using sys-firewall as UpdateVM to download updates for Dom0; this may take some 
time...
Using sys-firewall as UpdateVm to download updates for Dom0; this may take some 
...
Qubes Templates repository 66 B/s | 169 B 00:02
Failed to synchronize cache for repo 'qubes-dom0-current', ignoring this repo.
Failed to synchronize cache for repo 'qubes-templates-itl', ignoring this repo.
Last Metadata expiration check: 0:03:13 ago on Fri Nov 9 18:32:21 2018.
Dependencies resolved.
Nothing to do.
Complete!
No packages downloaded



I can confirm this is not a hardware issue as I am trying it on a t450p and 
t450s, two complete different laptops.

I've tried trouble shooting this for the past 10 hours and i still don't know 
what I am doing wrong. I've tried so many suggested tips. http to https, mod 
yum repo, and others i've alrady forgotten i'm sure im probably looking in the 
wrong place. please anyone who can lead me to fixing this issue i would greatly 
appreciate it.

-- 
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/d051099c-4239-4f68-8a05-0b863e74eec6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] Re: Qubes 3.2: No Internet Connection, neither with Wi-Fi, neither with Ethernet. HELP PLEASE!

2018-11-09 Thread Stuart Perkins



On Fri, 9 Nov 2018 10:45:06 -0500
LMiller M <56lmil...@gmail.com> wrote:

>Ok back with the laptop. During boot up, dom0 green state, sys-net green
>state. WiFi connection good, and can reboot! Lol
>
>But with that said nothing else auto loads. I have to start fedora-26 and
>it will.
>
>When trying to start sys-firewall I get error ( PCI device 02:00.0 is in
>use by driver xenlight domain sys-net
>Log: /var/log/libvirt/libxl/libxl-driver.log
>
>I don’t see this log listed with sys-net, there are no logs with
>sys-firewall. I don’t see this listed in the Qubes log either.
>
>I have looked up help, but others have usb issues. I don’t have any
>attached and not trying to do anything with them as stated .
>
>I tried command qvm-pci attach —persistent —option permissive=True —option
>no-strict-reset
>
>But I’m missing something so it’s not working. I’m in the right direction?
>I need to reset pci and set no restrictions?
>
>
>On Wed, Nov 7, 2018 at 9:32 PM LMiller M <56lmil...@gmail.com> wrote:
>
>> Ok so I figured out how to see the logs.
>>
>> I have been able to figure out why the laptop wasn’t responding to the OS
>> correctly. Now it’s working and updating as needed.
>>
>> I will explain more as I learn more.
>>
>> I do appreciate the guidance. I think there is more that can be shown, to
>> help newbies.
>>
>> I’m going to put something together from my view point to see if you all
>> agree. Maybe it can be useful to all new qube users like me. Lol anyway, I
>> wouldn’t have figured it out as fast for myself with out your help.
>>
>> Thank you for helping me.
>>
>> I’m still figuring things out, but this build is awesome and so much to
>> learn with it.
>> On Tue, Nov 6, 2018 at 4:43 PM LMiller M <56lmil...@gmail.com> wrote:
>>
>>> Ok on first boot after install Qubes will show the kernel failure and
>>> bypass and boot into dom0.
>>>
>>> Once there, in the Qubes manager dom0 has green state.
>>>
>>> Lol ok don’t laugh too hard. So I checked devices like have been, sys-net
>>> as you mentioned. Both Ethernet and WiFi devices are there. So I just
>>> removed my Ethernet from device selection and bingo sys-net green state!
>>>
>>> So I will try now to run system updates for dom0 and fedora.
>>>
>>> Thanks again for point things out. Sometimes you look at something so
>>> crazy and just need a second thought.
>>>
>>> So, can you show me how to check logs if I run into issues? Lol please
>>> and thanks
>>> On Tue, Nov 6, 2018 at 4:09 PM 'awokd' via qubes-users <
>>> qubes-users@googlegroups.com> wrote:
>>>

 LMiller M:
 > Update: Kernel failure during boot install OS 4.0
 >
 > After the install booted into dom0, checking Qubes kernel package to
 see
 > what three were stored or available. Mine only list one kernel.
 >
 > 4.14.18-1
 >
 > I checked using the rpm -qa ‘kernel-Qubes-vm*’
 >
 > Using the install update option I get:
 >
 > Unable to reset pci device :03:00.2:
 >
 > Trying to apply the device to the selected box: error: device tab:
 can’t
 > attach pci device to VM in pvh mode
 >
 > Does that mode need to be changed?
 >
 > Stupid question but because honestly I don’t know. How do you check the
 > logs? I’m the terminal?
 >
 > I downloaded the new kernel to cd, can install from the cd? I don’t see
 > anything on the Qubes kernel page except download from internet throw
 > Qubes. With internet I can’t.
 >
 >
 > On Tue, Nov 6, 2018 at 10:39 AM LMiller M <56lmil...@gmail.com> wrote:
 >
 >> So, after looking more into the kernel issue. I see on the Qubes site
 some
 >> instructions for trying to change the kernel. I’m going to do a
 reinstall
 >> of the 4.0 os to get back into Dom0 and try it out. I will post back
 >> hopefully with success..
 >> On Mon, Nov 5, 2018 at 8:02 PM LMiller M <56lmil...@gmail.com> wrote:
 >>
 >>> Ok so one more if I can please, this is on a Asus K56c laptop and it
 has
 >>> a kernel failure on boot with Qubes Os 4.0. On the first install it
 shows
 >>> the kernel failure and it boots to the OS don0. If I turn off or
 reboot it
 >>> shows my kernel failure and won’t load into the os.
 >>>
 Glad you got your other computer working at least! So on this one, where
 are you getting this kernel failure exactly? If it's booting to dom0,
 I'm not following where you're having trouble. There's a message on boot
 about failed to load kernel modules that can be safely ignored.

 To update dom0, you want to use "sudo qubes-dom0-update". You should
 rarely need to update the kernel by itself.

 Is that when you are getting the PCI reset error? Is your sys-net
 started? Check in Qube Manager. Then, check sys-net's Qube
 Settings/Devices to see what's attached there and if 03:00.2 is one of
 the devices. If so, see what it is.

 --
 

[qubes-users] Re: Failed to synchronize cache for repo 'qubes-dom0-cached', disabling.

2018-11-09 Thread alrojs
On Friday, November 9, 2018 at 2:25:26 PM UTC-8, Otto Kratik wrote:
> On Friday, November 9, 2018 at 3:42:40 PM UTC-5, alrojs wrote:
> > On Friday, October 5, 2018 at 11:48:01 AM UTC-7, Otto Kratik wrote:
> > > Qubes 3.2
> > > 
> > > Ever since a routine qubes-dom0-update was interrupted in the middle of 
> > > the upgrade process, I can no longer run any updates on dom0. Instead I 
> > > see the message:
> > > 
> > > "Failed to synchronize cache for repo 'qubes-dom0-cached', disabling."
> > > 
> > > ..in response to most commands that I attempt through 
> > > yum/dnf/qubes-dom0-update to try fixing it. None of the usual approaches 
> > > like --clean have been successful.
> > > 
> > > What should I try from here to correct the issue?
> > > 
> > > Thanks,
> > > Otto
> > 
> > hello,
> > 
> > I'm having the same issue.
> > 
> > dom0 fails to synchronize cache for repo 'qubes-dom0-current' and 
> > 'qubes-template-itl'. 
> > 
> > I've tried the steps recommended above and the proxy seems to be opperating 
> > fine but whenever i try to update i am unable to.
> > 
> > My main goal is the get qubes-u2f working which wont' because it fails to 
> > synchronize.
> 
> 
> It's been a few weeks, but I believe the synchronize cache issue resolved 
> itself the next time I forcibly installed something on dom0 using yum/dnf or 
> qubes-dom0-update. I don't remember which package I installed or reinstalled, 
> but forcing it to perform an install from a repo that *was* working seemed to 
> refresh everything again.
> 
> In my case the stuck pseudo-repo was the local qubes-dom0-cached one, so if 
> qubes-dom-current isn't working I'm not sure the same procedure will be 
> workable.
> 
> I'd go back and check my command line history, but I ended up having to 
> reinstall the entire OS shortly afterward since the glitch that caused the 
> entire situation in the first place (interrupted kernel update) was 
> irrecoverable.

thanks for a quick update, guess i'll have to try to reproduce this.

I'm on my third install and this issue has persisted through my 3 installs. My 
current install is pretty bare and still I see this issue.

first two installs was 4.0 and now currently on 4.0.1-rc1
hardware t450s

-- 
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/e228838b-98ae-4406-94ae-1cc53973b157%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Fedora-29-minimal :: Feedback / Using it as sys-Template

2018-11-09 Thread 799
Hello,

I tried to use the new fedora-29-minimal template as base for my sys-vms
and run into two problems:

1) the network manager icon look different like two icons are overlaying
2) No network connectivity even when the Wifi is connected.

If I run the same script to prepape a sys-vms based on a fedora-28-minimal
template, everything is working fine.

Can someone retry this and create a working sys-vm template which is based
on fedora-29-minimal?

Im using the following script from dom0 to built my sys-vm-template:

# Create a new template which is based on the fedora-29-minimal template
qvm-clone fedora-29-minimal t-fedora-29-sys
# install additional package which are needed for sys-vms (sys-net /
sys-firewall / sys-usb):
qvm-run --auto --user root t-fedora-29-sys "xterm -hold -e 'dnf -y install
qubes-core-agent-qrexec qubes-core-agent-systemd
qubes-core-agent-networking polkit qubes-core-agent-network-manager
notification-daemon qubes-core-agent-dom0-updates qubes-usb-proxy
network-manager-applet NetworkManager-wwan NetworkManager-wifi
iwl6000g2a-firmware qubes-input-proxy-sender && \
shutdown -h now'"
# shutdown all VMs
qvm-shutdown --all --wait --timeout 120

#Switch template for my sys-VMs to the new template
qvm-prefs --set sys-usb template t-fedora-28-sys
qvm-prefs --set sys-net template t-fedora-28-sys
qvm-prefs --set sys-firewall template t-fedora-28-sys

#restart firewall (will also start sys-net)
qvm-start sys-firewall

- O

-- 
You received this message because you are subscribed to the Google Groups 
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to qubes-users+unsubscr...@googlegroups.com.
To post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/CAJ3yz2srT%2BkqfzRZKPEgkALN4-BxHtwzRwxYEfMPchH-AUCggA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Re: Failed to synchronize cache for repo 'qubes-dom0-cached', disabling.

2018-11-09 Thread Otto Kratik
On Friday, November 9, 2018 at 3:42:40 PM UTC-5, alrojs wrote:
> On Friday, October 5, 2018 at 11:48:01 AM UTC-7, Otto Kratik wrote:
> > Qubes 3.2
> > 
> > Ever since a routine qubes-dom0-update was interrupted in the middle of the 
> > upgrade process, I can no longer run any updates on dom0. Instead I see the 
> > message:
> > 
> > "Failed to synchronize cache for repo 'qubes-dom0-cached', disabling."
> > 
> > ..in response to most commands that I attempt through 
> > yum/dnf/qubes-dom0-update to try fixing it. None of the usual approaches 
> > like --clean have been successful.
> > 
> > What should I try from here to correct the issue?
> > 
> > Thanks,
> > Otto
> 
> hello,
> 
> I'm having the same issue.
> 
> dom0 fails to synchronize cache for repo 'qubes-dom0-current' and 
> 'qubes-template-itl'. 
> 
> I've tried the steps recommended above and the proxy seems to be opperating 
> fine but whenever i try to update i am unable to.
> 
> My main goal is the get qubes-u2f working which wont' because it fails to 
> synchronize.


It's been a few weeks, but I believe the synchronize cache issue resolved 
itself the next time I forcibly installed something on dom0 using yum/dnf or 
qubes-dom0-update. I don't remember which package I installed or reinstalled, 
but forcing it to perform an install from a repo that *was* working seemed to 
refresh everything again.

In my case the stuck pseudo-repo was the local qubes-dom0-cached one, so if 
qubes-dom-current isn't working I'm not sure the same procedure will be 
workable.

I'd go back and check my command line history, but I ended up having to 
reinstall the entire OS shortly afterward since the glitch that caused the 
entire situation in the first place (interrupted kernel update) was 
irrecoverable.

-- 
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/13d9c2fa-3080-46f4-87e9-bd5ca833d986%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] Qubes 4: Unable to get any DVM app to ever launch

2018-11-09 Thread Otto Kratik
On Tuesday, November 6, 2018 at 10:29:49 AM UTC-5, unman wrote:
> On Mon, Nov 05, 2018 at 01:56:00PM -0800, Otto Kratik wrote:
> > > Thanks for the extensive troubleshooting.
> > > 
> > > It looks as if there's a problem *either* with the service *or* with the
> > > desktop files on fedoratest.
> > > Can you check the contents of /etc/qubes/rpc/policy/qubes.StartApp to
> > > make sure that you dont have a "deny" statement at the top of that file?
> > > You could temporarily insert a line at the top:
> > > dom0 $anyvm allow
> > > $anyvm $anyvm allow
> > > 
> > > Just concentrate on using:
> > > qvm-run -a --service --dispvm=fedoratest -- qubes.StartApp+firefox (or
> > > gedit)
> > > Check the log file in /var/log/qubes : you should see a log created for
> > > whatever dispVM is atrted and qubes.log updated.
> > > 
> > > unman
> > 
> > 
> > So during testing, even though I'd stopped all other VMs from running, I 
> > started noticing some odd slowdowns and other memory-related issues, 
> > wondered if RAM shortage was affecting my attempts, and decided to reboot 
> > and try again from scratch with no autostart VMs enabled.
> > 
> > After that, I am now able to run pretty much any app in a Debian or Whonix 
> > based DispVM without issue. In Fedora based DVMs, some apps like Firefox, 
> > Filezilla, Calculator etc all run fine from the DVM menu, while other apps 
> > such as Gedit and Nautilus/Files simply don't seem to want to act as the 
> > "launch leaders" for DispvM's. 
> > 
> > Meaning, the DispVM gets launched, but those apps don't open, and then the 
> > DVM halts again a minute or so later, as previously described. If I launch 
> > Firefox instead first in a Fedora DVM, and then from the widget select "Run 
> > terminal" for that very same already-open DVM, I can then launch Gedit or 
> > Nautilus or any other app from the command line without any problem. But 
> > those apps won't open as the initial "launch-apps" for Fedora DVMs.
> > 
> > By contrast, in Debian DVM's I can launch KWrite or Dolphin or whatever 
> > other equivalents easily, a well as Firefox or Tor Browser, and so far 
> > haven't found one that refuses to launch. 
> > 
> > Thus it seems like a bit of an interoperability quirk between Fedora26 and 
> > the DVM system, so far as I can tell. Results are the same whether trying 
> > from gui menu or dom0 command line, though admittedly with some apps like 
> > Gedit, I am unsure which of the following I should be typing:
> > 
> > qvm-run -a --service --dispvm=fedoratest -- qubes.StartApp+gedit
> > qvm-run -a --service --dispvm=fedoratest -- qubes.StartApp+org.gnome.gedit
> > qvm-run -a --service --dispvm=fedoratest -- "qubes.StartApp+Text Editor"
> > 
> > All of them fail in the same way, however.. so I'm not sure it makes much 
> > difference.
> > 
> > Out of curiosity for comparison, are you able to launch Gedit or 
> > Nautilus/Files in a Fedora based DVM without issue, as the initial 
> > launch-app either from the menu or command line?
> > 
> 
> I'm glad that some progress is being made.
> I wonder if there's some issue with the desktop files in Fedora which
> are preventing those applications from running? Those symptoms are
> exactly those that fit with problems with the desktop files.
> I dont have Fedora here to test, I'm afraid: Debian and BSD only.
> 
> If you open a Fedora based qube, do the applications work if you try to
> open files that would use them? I mean create text file, and then double
> click on it in nautilus, etc etc
> 
> unman


If I run a fedora based qube normally, all of those applications open and run 
completely fine, whether I launch them on their own or open files that would 
naturally use them as their default handlers. Gedit and Nautilus etc are 
perfectly willing to act at launch-starters for a fedora based qube, as long as 
that qube is a regular AppVM and not a DVM-template.

It is *only* when trying to open those apps as launch-starters from DVM 
templates (such as fedora-26-DVM) that they refuse to open. Other apps like 
Firefox/Calculator open fine as launch-starters for fedora DVM's, and once 
open, I can run-terminal from the widget for that Disp8375 or whatever, and 
from that terminal launch Gedit or Nautilus or whatever, no problem.

Only trying to start a new fedora based DVM with some specific apps (gedit, 
nautilus) fails, with the Disp7473 halting a minute or so after it initially 
launches, without ever opening the requested app. Debian/Whonix DVM's seem to 
have no such issue with any apps, at least that I've noticed. Only fedora.

Honestly, it's a tiny bit of an inconvenience but at this point it's far more 
of an odd minor quirk than a major show-stopping issue, and thus I'm not sure I 
want to take up more of your or anyone else's troubleshooting time on something 
so relatively inconsequential. At the beginning I couldn't launch any DVM of 
any type no matter what, but I think that was more an available-memory issue 
than 

[qubes-users] Re: Failed to synchronize cache for repo 'qubes-dom0-cached', disabling.

2018-11-09 Thread appleonamadev
On Friday, October 5, 2018 at 11:48:01 AM UTC-7, Otto Kratik wrote:
> Qubes 3.2
> 
> Ever since a routine qubes-dom0-update was interrupted in the middle of the 
> upgrade process, I can no longer run any updates on dom0. Instead I see the 
> message:
> 
> "Failed to synchronize cache for repo 'qubes-dom0-cached', disabling."
> 
> ..in response to most commands that I attempt through 
> yum/dnf/qubes-dom0-update to try fixing it. None of the usual approaches like 
> --clean have been successful.
> 
> What should I try from here to correct the issue?
> 
> Thanks,
> Otto

hello,

I'm having the same issue.

dom0 fails to synchronize cache for repo 'qubes-dom0-current' and 
'qubes-template-itl'. 

I've tried the steps recommended above and the proxy seems to be opperating 
fine but whenever i try to update i am unable to.

My main goal is the get qubes-u2f working which wont' because it fails to 
synchronize.

-- 
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/f81adb6d-c2d2-4e40-820b-60fb7a36e617%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] Re: The state of the HiDPI display support in Qubes

2018-11-09 Thread Achim Patzner
Am Donnerstag, den 01.11.2018, 11:20 -0700 schrieb ka...@transmuted.io:
> I feel this situation would get better once Xfce finishes their GTK3
> porting. They are at 80% right now and GTK3 supports HiDPI natively
> and then Qubes will need help porting their Window decoration system
> to the new interface if required (I haven't looked at it yet).

I'm still owing you an answer on this...

Trying to solve this somewhere at the level of GTK is a bit late and it
will not help applications flying lower.

I'm a dinosaur. I'm coming from a time without all that stuff where X11
(finally version 1.1! yeah!) came with The Window Manager (twm) and the
scaling was controlled by starting X with the correct settings for dpi
and position in your x11.conf.

I'm still living in that age as I'm using lots of stuff that is still
stuck in the age of Motif. My weapon of choice is the terminal and it
is coming as xterm (because you will find it everywhere) and if the X
server is configured correctly it will do miracles for you (just read 
the description at 
http://www.futurile.net/2016/06/14/xterm-setup-and-truetype-font-configuration/
for a good idea).

If you want this to be working well for you (including readable pop-up-
menus your X geometry has to be correct (and I don't think that gnome
is doing a better job there without that). You can of course set
parameters "by hand" in configuration files but it will not work easily
across monitors with different resolutions.


Achim


-- 
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/3c1a94658cce8f031b82caac5ae36e20ef230f85.camel%40noses.com.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] Re: Qubes 3.2: No Internet Connection, neither with Wi-Fi, neither with Ethernet. HELP PLEASE!

2018-11-09 Thread LMiller M
Ok back with the laptop. During boot up, dom0 green state, sys-net green
state. WiFi connection good, and can reboot! Lol

But with that said nothing else auto loads. I have to start fedora-26 and
it will.

When trying to start sys-firewall I get error ( PCI device 02:00.0 is in
use by driver xenlight domain sys-net
Log: /var/log/libvirt/libxl/libxl-driver.log

I don’t see this log listed with sys-net, there are no logs with
sys-firewall. I don’t see this listed in the Qubes log either.

I have looked up help, but others have usb issues. I don’t have any
attached and not trying to do anything with them as stated .

I tried command qvm-pci attach —persistent —option permissive=True —option
no-strict-reset

But I’m missing something so it’s not working. I’m in the right direction?
I need to reset pci and set no restrictions?


On Wed, Nov 7, 2018 at 9:32 PM LMiller M <56lmil...@gmail.com> wrote:

> Ok so I figured out how to see the logs.
>
> I have been able to figure out why the laptop wasn’t responding to the OS
> correctly. Now it’s working and updating as needed.
>
> I will explain more as I learn more.
>
> I do appreciate the guidance. I think there is more that can be shown, to
> help newbies.
>
> I’m going to put something together from my view point to see if you all
> agree. Maybe it can be useful to all new qube users like me. Lol anyway, I
> wouldn’t have figured it out as fast for myself with out your help.
>
> Thank you for helping me.
>
> I’m still figuring things out, but this build is awesome and so much to
> learn with it.
> On Tue, Nov 6, 2018 at 4:43 PM LMiller M <56lmil...@gmail.com> wrote:
>
>> Ok on first boot after install Qubes will show the kernel failure and
>> bypass and boot into dom0.
>>
>> Once there, in the Qubes manager dom0 has green state.
>>
>> Lol ok don’t laugh too hard. So I checked devices like have been, sys-net
>> as you mentioned. Both Ethernet and WiFi devices are there. So I just
>> removed my Ethernet from device selection and bingo sys-net green state!
>>
>> So I will try now to run system updates for dom0 and fedora.
>>
>> Thanks again for point things out. Sometimes you look at something so
>> crazy and just need a second thought.
>>
>> So, can you show me how to check logs if I run into issues? Lol please
>> and thanks
>> On Tue, Nov 6, 2018 at 4:09 PM 'awokd' via qubes-users <
>> qubes-users@googlegroups.com> wrote:
>>
>>>
>>> LMiller M:
>>> > Update: Kernel failure during boot install OS 4.0
>>> >
>>> > After the install booted into dom0, checking Qubes kernel package to
>>> see
>>> > what three were stored or available. Mine only list one kernel.
>>> >
>>> > 4.14.18-1
>>> >
>>> > I checked using the rpm -qa ‘kernel-Qubes-vm*’
>>> >
>>> > Using the install update option I get:
>>> >
>>> > Unable to reset pci device :03:00.2:
>>> >
>>> > Trying to apply the device to the selected box: error: device tab:
>>> can’t
>>> > attach pci device to VM in pvh mode
>>> >
>>> > Does that mode need to be changed?
>>> >
>>> > Stupid question but because honestly I don’t know. How do you check the
>>> > logs? I’m the terminal?
>>> >
>>> > I downloaded the new kernel to cd, can install from the cd? I don’t see
>>> > anything on the Qubes kernel page except download from internet throw
>>> > Qubes. With internet I can’t.
>>> >
>>> >
>>> > On Tue, Nov 6, 2018 at 10:39 AM LMiller M <56lmil...@gmail.com> wrote:
>>> >
>>> >> So, after looking more into the kernel issue. I see on the Qubes site
>>> some
>>> >> instructions for trying to change the kernel. I’m going to do a
>>> reinstall
>>> >> of the 4.0 os to get back into Dom0 and try it out. I will post back
>>> >> hopefully with success..
>>> >> On Mon, Nov 5, 2018 at 8:02 PM LMiller M <56lmil...@gmail.com> wrote:
>>> >>
>>> >>> Ok so one more if I can please, this is on a Asus K56c laptop and it
>>> has
>>> >>> a kernel failure on boot with Qubes Os 4.0. On the first install it
>>> shows
>>> >>> the kernel failure and it boots to the OS don0. If I turn off or
>>> reboot it
>>> >>> shows my kernel failure and won’t load into the os.
>>> >>>
>>> Glad you got your other computer working at least! So on this one, where
>>> are you getting this kernel failure exactly? If it's booting to dom0,
>>> I'm not following where you're having trouble. There's a message on boot
>>> about failed to load kernel modules that can be safely ignored.
>>>
>>> To update dom0, you want to use "sudo qubes-dom0-update". You should
>>> rarely need to update the kernel by itself.
>>>
>>> Is that when you are getting the PCI reset error? Is your sys-net
>>> started? Check in Qube Manager. Then, check sys-net's Qube
>>> Settings/Devices to see what's attached there and if 03:00.2 is one of
>>> the devices. If so, see what it is.
>>>
>>> --
>>> You received this message because you are subscribed to a topic in the
>>> Google Groups "qubes-users" group.
>>> To unsubscribe from this topic, visit
>>> 

Re: [qubes-users] Using an OnlyKey

2018-11-09 Thread pkraskov
> So the way mine works is actually consistent with using it on non-Qubes 
> systems. I insert the onlykey, and it blinks a little, and then no lights 
> display. I can then enter my PIN and the green light will go on. At that 
> point the onlykey will output info from any of the buttons, but TOTP won't 
> work. Then I open the onlykey app and then TOTP will work as well.

>I used info from this page 
>https://www.qubes-os.org/doc/usb/#how-to-use-a-usb-keyboard to get the OnlyKey 
>to operate as a USB keyboard.

What kernel version do you have? Did LED start working after you modified 
/etc/qubes-rpc/policy/qubes.InputKeyboard or it was working even before?

Mine OnlyKey still works with other OSes but doesn't work in Qubes for some 
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/b11f6bd8-f496-4828-9911-197b5f575f4e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] Qubes menu failing. Come on guys

2018-11-09 Thread Steve Coleman

On 11/8/18 7:45 AM, unman wrote:

On Wed, Nov 07, 2018 at 08:14:23PM -0800, Ryan Tate wrote:



The latest is everything above and below the VMs is gone from the Qubes menu. The bottom 
of the menu where I'd go to shut down just says "No applications found." The 
top where I would go to find settings, Qubes Manager, even the dom0 Terminal is just 
gone. So I don't even know how to debug. I've rebooting several times, it keeps happening.



Had you made any changes to the menu system?
Can you check the contents of /etc/xdg/menus/xfce-applications.menu to
make sure you still have a Menu item for System Tools. If you're not
sure just post the contents here.

There was a problem in the past with .desktop files disappearing.
can you make sure that you have .desktop files in
/usr/share/applications ?

unman


There is one consistently reproducible way to destroy the Qubes menu, by 
simply using the built in xfce/other menu editor to reorganize your menu 
entries, if you happen to be the impatient type in trying to get it 
done. I have tried every menu editor I could find, and they all seem to 
do pretty much the same damage.


Example:
1) Right click on the xfce/Qubes menu button.
2) Select properties from the popup menu
3) Select the edit menu button.
4) Select a sub-menu for any VM to edit
5) Select an entry on the right to move an application up/down in the list
6) Press the up or down button quickly in succession, say to move an 
entry from the bottom of the list, up to the top of the list.

7) Save the menu.

Congratulations, you now have no Qubes menu at all, so lets hope you 
still have a dom0 command window open.


To recover the menu, start a template vm via qvm-run, and run dnf to 
update or make any change that in turn forces a dom0 resync of the Qubes 
menu items. Or perhaps you can just force a resync from the dom0 command 
line (qvm-sync-appmenus), but I have not tested that.


I believe (a wild *** guess, base on only visual clues and behavioral 
evidence) the problem is that the editor rewrites a file upon each 
'move' button click, and if you do it too quickly there is a concurrency 
problem with re-opening the menu files that have not yet been 
closed/flushed to disk. They may be reading and updating a partially 
written menu file.


Do the same thing slowly and count-to-3 between mouse clicks, and there 
is no problem. If you can hear your disk drive churning when clicking 
the up/down button, when its quiet again, then it is ok to push the 
button again.


I'm guessing this is an upstream xfce read/write/thread locking problem, 
but the added complexity of the Qubes menu might be the reason for the 
concurrency/timing issue due to more complexity overhead and Xen CPU 
latencies. I'm guessing if you had a very simple xfce menu (e.g. the 
default/simple xfce OS installation), and without Xen overhead, this 
would likely not happen, thus the proper locking had never been 
implemented. I have not yet had the luxury of the time to chase this 
thread, to actually confirm my suspicion, so your mileage may vary. On 
my system this is 100% reproducible.


Bottom line, don't be too quick with changes to the menu, or you will be 
spending even more time repairing your system. The first time this 
happened I had no clue how to recover.



Steve

--
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/ca6434a7-3581-9250-8817-89a749f4f294%40jhuapl.edu.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] Where is Chrome once installed?

2018-11-09 Thread pieter lems
Which method was it. It can be handy if other users can also profit if they
run into the same problem. Glad you fixed it!

On Fri, Nov 9, 2018, 3:06 PM William Fisher  wrote:

> I tried 3 different methods last night, finally one worked and it showed
> up for me this morning after restart.
>
> Thanks
>
> On Fri, Nov 9, 2018 at 8:01 AM unman  wrote:
>
>> On Thu, Nov 08, 2018 at 08:35:59PM -0800, William Fisher wrote:
>> > I tried that command in Qubes 4. I created a VM for chrome and started
>> it using the Chrome App listed on the VM and nothing. No Chrome, no
>> errors no nothing!
>> >
>>
>> You have trimmed the previous material so it's completely unclear what
>> you are referring to. :-(
>>
>> This works for me:
>> In Templates:
>> Debian - sudo apt install chromium
>>
>> Fedora - Download rpm from chrome site and install using 'dnf install
>> chromerpm'
>>
>> Creating qubes based on these templates produces correct menu items ,
>> and selecting the menu item starts the qube and opens chrome (or
>> chromium)
>>
>> It seems that this hasn't worked for you.
>> Can you please say what template you have are using, and what steps you
>> took
>> to install chrome.
>>
>> unman
>>
>>
>>
>>
>>
>>
>> --
>> 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/vYRrfdp05RA/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/20181109140141.ky5k3artaavx5ytj%40thirdeyesecurity.org
>> .
>> 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/CAJyh_i-PY58kWvh4GDZg6YpSJ%2BXYD-AKzwF-femWE_LgYtg8rQ%40mail.gmail.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/CAK8vAnUpJA1bw_F1vdC-UTS164CY%3DzTdrBcJq9eo5rGaeQB_KA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] Qubes OS 4.0, full screen and HVM domain

2018-11-09 Thread unman
On Fri, Nov 09, 2018 at 01:11:53AM -0800, gdru...@gmail.com wrote:
> Hi,
> 
> I'm trying to enable full screen mode two standalone VM(s).
> 
> The following modus operandi does not work : 
> https://www.qubes-os.org/doc/full-screen-mode/
> 
> No error displayed and no change right-clicking on a window’s title bar and 
> selecting "Fullscreen".
> 
> How can I fix it ?
> 
> Any help and advice would be greatly appreciated.
> 
> Best regards.
> 
> GD Rub
> 

You dont say what the standaloneVMs are:
On a Debian based HVM the simplest thing to do (under Xfce) is to set
the display size in the HVM to that of the screen (or larger) and then select
Fullscreen from the title bar.
The same works in a Windows HVM.

That works for me.ymmv




-- 
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/20181109142036.djhdld42qfk6rg6g%40thirdeyesecurity.org.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] Where is Chrome once installed?

2018-11-09 Thread William Fisher
I tried 3 different methods last night, finally one worked and it showed up
for me this morning after restart.

Thanks

On Fri, Nov 9, 2018 at 8:01 AM unman  wrote:

> On Thu, Nov 08, 2018 at 08:35:59PM -0800, William Fisher wrote:
> > I tried that command in Qubes 4. I created a VM for chrome and started
> it using the Chrome App listed on the VM and nothing. No Chrome, no
> errors no nothing!
> >
>
> You have trimmed the previous material so it's completely unclear what
> you are referring to. :-(
>
> This works for me:
> In Templates:
> Debian - sudo apt install chromium
>
> Fedora - Download rpm from chrome site and install using 'dnf install
> chromerpm'
>
> Creating qubes based on these templates produces correct menu items ,
> and selecting the menu item starts the qube and opens chrome (or
> chromium)
>
> It seems that this hasn't worked for you.
> Can you please say what template you have are using, and what steps you
> took
> to install chrome.
>
> unman
>
>
>
>
>
>
> --
> 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/vYRrfdp05RA/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/20181109140141.ky5k3artaavx5ytj%40thirdeyesecurity.org
> .
> 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/CAJyh_i-PY58kWvh4GDZg6YpSJ%2BXYD-AKzwF-femWE_LgYtg8rQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] Where is Chrome once installed?

2018-11-09 Thread unman
On Thu, Nov 08, 2018 at 08:35:59PM -0800, William Fisher wrote:
> I tried that command in Qubes 4. I created a VM for chrome and started it 
> using the Chrome App listed on the VM and nothing. No Chrome, no errors 
> no nothing!
> 

You have trimmed the previous material so it's completely unclear what
you are referring to. :-(

This works for me:
In Templates:
Debian - sudo apt install chromium

Fedora - Download rpm from chrome site and install using 'dnf install
chromerpm'

Creating qubes based on these templates produces correct menu items ,
and selecting the menu item starts the qube and opens chrome (or
chromium)

It seems that this hasn't worked for you.
Can you please say what template you have are using, and what steps you took
to install chrome.

unman 






-- 
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/20181109140141.ky5k3artaavx5ytj%40thirdeyesecurity.org.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] Qubes menu failing. Come on guys

2018-11-09 Thread unman
On Thu, Nov 08, 2018 at 07:27:02PM -0800, cooloutac wrote:
> On Thursday, November 8, 2018 at 11:55:45 AM UTC-5, pieter lems wrote:
> > I don't mean this in a bad way but isn't 4.0.1 a testing release? 
> > if you are using qubes for important things you should stick with 4.0 as
> >  of now. (it's also mentioned in the release notes) Devs are no 
> > wizards.  :)
> > I hope you get it working.
> > 
> > 
> > Op do 8 nov. 2018 om 13:45 schreef unman :
> > On Wed, Nov 07, 2018 at 08:14:23PM -0800, Ryan Tate wrote:
> > 
> > > I don't know what is going on with 4.0.1 but suddenly my machine is 
> > > haywire.
> > 
> > > 
> > 
> > > The latest is everything above and below the VMs is gone from the Qubes 
> > > menu. The bottom of the menu where I'd go to shut down just says "No 
> > > applications found." The top where I would go to find settings, Qubes 
> > > Manager, even the dom0 Terminal is just gone. So I don't even know how to 
> > > debug. I've rebooting several times, it keeps happening.
> > 
> > > 
> > 
> > > I know Qubes is fairly high maintenance but I had a nice groove going 
> > > with qubes 4 finally. Whatever updates you are pushing down with 4.0.1 
> > > updates are breaking my workflow left and right. First whonix got borked 
> > > now the Qubes menu is broken. I shudder to think what will be next to 
> > > fail. This is frustrating. Some of us are actually trying to get work 
> > > done in the OS.
> > 
> > > 
> > 
> > 
> > 
> > Hi Ryan
> > 
> > 
> > 
> > Are you using Xfce? (The default desktop environment in Qubes)
> > 
> > 
> > 
> > Had you made any changes to the menu system?
> > 
> > Can you check the contents of /etc/xdg/menus/xfce-applications.menu to
> > 
> > make sure you still have a Menu item for System Tools. If you're not
> > 
> > sure just post the contents here.
> > 
> > 
> > 
> > There was a problem in the past with .desktop files disappearing.
> > 
> > can you make sure that you have .desktop files in
> > 
> > /usr/share/applications ?
> > 
> > 
> > 
> > unman
> > 
> 
> pretty sure i'm using R4.0  how do i check from console I'm only getting this 
> from qube-manager
> 

You can check in /etc/fedora-release.

If you are missing the desktop files in /usr/share/applications, then
you can reload them from the installation disk - cooloutac has already
told you how to do that.

unman

-- 
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/20181109131517.rulhvevfhpaaqpke%40thirdeyesecurity.org.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] Where is Chrome once installed?

2018-11-09 Thread pieter lems
Did you install chrome in a template VM? If yes select the AppVM (in which
you want to use chrome) in the qube-manager and edit the settings so that
the AppVm uses chrome.
Hope this helps. Otherwise check out the tasks at the bottom of the page at
this link : https://www.qubes-os.org/doc/software-update-vm/

On Fri, Nov 9, 2018, 5:36 AM William Fisher  wrote:

> I tried that command in Qubes 4. I created a VM for chrome and started it
> using the Chrome App listed on the VM and nothing. No Chrome, no errors
> no nothing!
>
> --
> 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/55f59e53-3209-4469-9df0-d998e21ec88b%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/CAK8vAnVe%2BwhiJ7HjDxVXkQDQF8eYfPhsGzukT4n8vBtqJQKMmA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Qubes OS 4.0, full screen and HVM domain

2018-11-09 Thread gdrub51
Hi,

I'm trying to enable full screen mode two standalone VM(s).

The following modus operandi does not work : 
https://www.qubes-os.org/doc/full-screen-mode/

No error displayed and no change right-clicking on a window’s title bar and 
selecting "Fullscreen".

How can I fix it ?

Any help and advice would be greatly appreciated.

Best regards.

GD Rub

-- 
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/c192674c-6ee0-4ccf-9179-818469cac469%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.