also it was a cloned repo that I had manually upgraded. wouldn't know there
was no error. it would show it updating. unless I did the -v to see the
problems.
--
You received this message because you are subscribed to the Google Groups
"qubes-users" group.
To unsubscribe from this group and
I don't think so in my case.
regarding google chrome repo it was because I was forcing https over tor at the
time. and when it got updated it would keep reverting it back to http and then
failing. I would have to keep changing it back to https for it to update and
get rid of arrow.
In
when you update do -vv to show full information on update progress and see if
there is any errors.
This sometimes happens to me if google chrome repo doesn't update for example.
Last time I did this it showed metadata erros. so a sudo dnf clean metadata
fixed issue.
This may be related
On Monday, February 25, 2019 at 4:02:38 PM UTC-5, John Mitchell wrote:
> If I may ask what OS do you use for the host?
Guest the latest QSA answers this question somehwat lol.
--
You received this message because you are subscribed to the Google Groups
"qubes-users" group.
To unsubscribe from
ya most likely can be considered a security feature. Joanna has mentioned
herself in the past wallpaper images can compromise a system. Maybe not
purposely disabled but not worth to support either lol. Defeats purpose of
using Qubes with a dom0.
The only thing you really should be doing in
when you update do -vv to show full information on update progress and see if
there is any errors.
This sometimes happens to me if google chrome repo doesn't update for example.
Last time I did this it showed metadata erros. so a sudo dnf clean metadata
fixed issue.
--
You received
On Wednesday, March 6, 2019 at 12:08:15 AM UTC-5, Sphere wrote:
> I also did what Chris suggested as well as the dnf clean all and the result
> is all the same.
> No problem with my dns for sure because I'm using dnscrypt on a pool of 19
> dns servers and I've never had problems resolving
Today I have had another problem which I think indicates that the problem is
not only in Fedora 29, it could me in Qubes too.
So, I today I had a problem with encoding when I tried to open one of my .txt
file in 'gedit' editor.
To solve this problem I installed 'dconf-editor' package and
Hi Everyone
I just set up a Windows 7 Pro x64 VM and installed Qubes Windows Tools
successfully, including the disk driver.
I did Windows installation with this help:
https://www.qubes-os.org/doc/windows-vm/
And installation von QWT with this help:
https://www.qubes-os.org/doc/windows-tools/
On Wednesday, March 6, 2019 at 5:40:23 AM UTC+3, daniel wrote:
> I ran into this too, and as far as I can tell, it is a Fedora bug.
> The extant locales can be found with locale -a
> C.UTF-8 is not among them. So the default locale is installed! But
> C.utf8 is. You can set permanently by running
10 matches
Mail list logo
