onsdag den 20. marts 2019 kl. 13.33.27 UTC+1 skrev a...@it-minds.dk:
> Hello qubes users!
>
> I currently acquired this dock
> (https://www.dell.com/en-us/shop/dell-business-thunderbolt-dock-tb16-with-240w-adapter/apd/452-bcnu/pc-accessories),
> and tried to connect it with my laptop, but it doe
torsdag den 21. marts 2019 kl. 11.34.10 UTC+1 skrev David Hobach:
>
> True, that is somewhat more advanced though. State-level attackers have
> teams that can open and replace arbitrary hardware with malicious one
> within 15 mins, yes. So if you fear them, don't leave your laptop
> unattended
Hello qubes users!
I currently acquired this dock
(https://www.dell.com/en-us/shop/dell-business-thunderbolt-dock-tb16-with-240w-adapter/apd/452-bcnu/pc-accessories),
and tried to connect it with my laptop, but it does not seem to work.
I have found different posts here and there regarding the
Hello!
I have experienced a couple of times now that my Qubes 4 installation crashes
at different times.
I do not expect this to be an issue with Qubes, but it would be nice if I could
debug this some how. I have no idea where to look for the necessary logs though.
Some details:
The crash itse
onsdag den 5. december 2018 kl. 15.45.33 UTC+1 skrev Ranguvar:
> On Wed, Dec 5, 2018 at 3:56 AM aaq via qubes-users
> wrote:
> tirsdag den 4. december 2018 kl. 23.46.32 UTC+1 skrev Ranguvar:
>
> > On Tue, Dec 4, 2018 at 5:41 PM wrote:
>
> > Hey all!
>
> >
tirsdag den 4. december 2018 kl. 23.46.32 UTC+1 skrev Ranguvar:
> On Tue, Dec 4, 2018 at 5:41 PM wrote:
> Hey all!
>
>
>
> Using Qubes 4.0.1-rc1, been updating with qubes-dom0-update --releasever=4.0
>
>
>
> I installed @kde-desktop-qubes, and then later uninstalled it.
>
>
>
> This seems
mandag den 26. november 2018 kl. 12.46.29 UTC+1 skrev fabio_p7cc62u:
> I made an accidental edit to /etc/fstab which is causing my TemplateVM to
> timeout on boot with error Cannot connect to qrexec agent for 60 seconds
>
> Is there a way to edit a particular VM's etc/fstab without booting it
mandag den 19. november 2018 kl. 16.55.42 UTC+1 skrev 22...@tutamail.com:
> I recreated a new Appvm for my templates to use for updates. I currently use
> sys-whonix...the new template is sys-whonix-New.
>
>
> How would I do this?
Hey there!
I am not currently on my Qubes box, but I guess you
søndag den 18. november 2018 kl. 17.00.19 UTC+1 skrev Campbell:
> On install I chose UK English with US Keyboard. For some reason upon
> installation Qubes set my laptop keyboard to UK, even though I chose US
> keyboard during installation.
>
> My guess is that when Qubes set language to UK Engl
lørdag den 17. november 2018 kl. 23.44.01 UTC+1 skrev Vasilis:
> Hi,
>
> It seems that the i3 window manager has been in the testing repository for a
> while, and I don't see many bug reports or posts on the mailing lists with
> problems associated to the i3 window manager.
>
> Anything else requ
lørdag den 17. november 2018 kl. 22.26.00 UTC+1 skrev Black Beard:
> Hey community,
>
> i hope, that someone can help me by following probleme.
>
> My main OS is Qubes 4.0. No Dual-boot or other stuff. Only Qubes 4.0
> installed.
>
> My target:
>
> Install Chuckoo Sandbox in Virtualbox on Debi
lørdag den 17. november 2018 kl. 17.01.02 UTC+1 skrev Patrick Schleizer:
> Franz:
> > I succesfully updated to whonix 14, when the VM start a message tells:
> > "connected to tor" making me happy, But if I ping google I get:
> >
> > user@host:~$ ping google.com
> > PING google.com (216.58.207.206)
Hello!
So, I switched to KDE as you can see in some other threads, and honestly I like
it way better than XFCE.
My biggest issue right now however is, that the network manager applet does not
show in KDE. I get notification when I start my session that I am connected to
my network, and I do ha
tirsdag den 13. november 2018 kl. 12.26.58 UTC+1 skrev unman:
> On Tue, Nov 13, 2018 at 12:00:40AM -0800, aaq via qubes-users wrote:
> > Hello!
> >
> > I have broken the GUI in dom0 in some weird way.
> > I tried to install KDE, then I tried to remove it again, befor
Hello!
I have broken the GUI in dom0 in some weird way.
I tried to install KDE, then I tried to remove it again, before realising that
I was fine with having it. Unfortunately, when I wanted to reinstall it, dnf
kept saying that I already had the group installed, so I couldn't just run the
`sud
mandag den 12. november 2018 kl. 03.10.59 UTC+1 skrev 22...@tutamail.com:
> Thank you both for the comments...
>
> In the message I remember a statement: "..This menu allows you to
> select...automatic run for, if any...running grub-install automatically is
> recommended". I believe it also sai
mandag den 12. november 2018 kl. 01.03.18 UTC+1 skrev unman:
> On Sun, Nov 11, 2018 at 09:54:08AM -0800, aaq via qubes-users wrote:
> > søndag den 11. november 2018 kl. 17.17.27 UTC+1 skrev a...@it-minds.dk:
> > > Hello everybody!
> > >
> > > I wanted to try
søndag den 11. november 2018 kl. 17.17.27 UTC+1 skrev a...@it-minds.dk:
> Hello everybody!
>
> I wanted to try out KDE with Qubes 4, but found that it was simply too much
> compared to my needs.
>
> Unfortunately, removing KDE again isn't as simple as installing it. My
> biggest issues is that
søndag den 11. november 2018 kl. 18.28.06 UTC+1 skrev 22...@tutamail.com:
> I just updated my Debian template and received a "Configuring grub-pc" window
> in my terminal, through trial and error I discovered that I was able to
> select "OK", and select configurations using the curser arrows and
Hello everybody!
I wanted to try out KDE with Qubes 4, but found that it was simply too much
compared to my needs.
Unfortunately, removing KDE again isn't as simple as installing it. My biggest
issues is that it hijacked some core components across the system, even though
I am not using KDE (s
Den torsdag den 25. januar 2018 kl. 20.17.48 UTC+1 skrev Kevin Martinsen:
> i3 has been working fine for me.
>
> Did you follow the installation instructions on
> https://www.qubes-os.org/doc/i3/? Specifically:
> $ sudo qubes-dom0-update --enablerepo=qubes-dom0-current-testing
> i3-settings-qub
Den torsdag den 25. januar 2018 kl. 14.40.14 UTC+1 skrev WolfSkin:
> On Thursday, 25 January 2018 13:36:18 UTC, WolfSkin wrote:
> > Basically my issue is that I am getting a kernel panic when I try
> > installing qubes-os on my laptop both in UEFI and legacy mode.
> > The kernel panic can be see
Hey all,
I installed i3 when first set up my machine, but I can't seem to get it
working..
Has anyone else experienced issues with i3?
In my case, no applets are shown in the bar and I cannot start any programs
from VM's (any VM).
If I run qvm-ls, it shows that VM's are running, and if I try
Den tirsdag den 23. januar 2018 kl. 18.36.00 UTC+1 skrev Krišjānis Gross:
> Hi,
>
> I am trying to build a custom installation .iso. I have an issue that I have
> purchased a new set of hardware that does not work with the current builds of
> qubes. I am trying to build the most updated version
Den lørdag den 6. januar 2018 kl. 12.27.18 UTC+1 skrev Tom Zander:
> On Saturday, 6 January 2018 00:11:43 GMT Franz wrote:
> > I would add some way to make some order in the
> > applVM list, so that a standard view may show only the most commonly used
> > VMs, while rarely used VMs are hidden and s
Den fredag den 19. januar 2018 kl. 16.39.31 UTC+1 skrev Marek
Marczykowski-Górecki:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> On Fri, Jan 19, 2018 at 06:53:55AM -0800, aaq via qubes-users wrote:
> > Den fredag den 19. januar 2018 kl. 15.48.08 UTC+1 skre
Den fredag den 19. januar 2018 kl. 15.48.08 UTC+1 skrev a...@it-minds.dk:
> Den fredag den 19. januar 2018 kl. 15.44.35 UTC+1 skrev awokd:
> > On Fri, January 19, 2018 2:33 pm, aaq via qubes-users wrote:
> > > Den fredag den 19. januar 2018 kl. 15.28.27 UTC+1 skrev awokd:
&
Den fredag den 19. januar 2018 kl. 15.44.35 UTC+1 skrev awokd:
> On Fri, January 19, 2018 2:33 pm, aaq via qubes-users wrote:
> > Den fredag den 19. januar 2018 kl. 15.28.27 UTC+1 skrev awokd:
> >
> >> On Fri, January 19, 2018 1:48 pm, aaq via qubes-users wrote:
>
Den fredag den 19. januar 2018 kl. 15.28.27 UTC+1 skrev awokd:
> On Fri, January 19, 2018 1:48 pm, aaq via qubes-users wrote:
> > Den fredag den 19. januar 2018 kl. 14.44.26 UTC+1 skrev a...@it-minds.dk:
> >
> >> Den fredag den 19. januar 2018 kl. 14.08.21 UTC+1 skrev T
Den fredag den 19. januar 2018 kl. 14.44.26 UTC+1 skrev a...@it-minds.dk:
> Den fredag den 19. januar 2018 kl. 14.08.21 UTC+1 skrev Tom Zander:
> > On Friday, 19 January 2018 11:48:56 CET aaq via qubes-users wrote:
> > > What can I do
> >
> > Could this have s
Den fredag den 19. januar 2018 kl. 14.08.21 UTC+1 skrev Tom Zander:
> On Friday, 19 January 2018 11:48:56 CET aaq via qubes-users wrote:
> > What can I do
>
> Could this have something to do with the broken qmemman?
>
> Try turning off memory-management and give the sys-net
Qubes 4 RC3
So, I updated using current testing yesterday, and there was an update to qubes
core dom0 and other changes..
Network worked fine before I shutdown my machine, but now when I try to start
sys-net I get an error saying "Not enough memory to start domain 'sys-net'"
I have tried reboo
Den fredag den 12. januar 2018 kl. 12.38.20 UTC+1 skrev awokd:
> On Fri, January 12, 2018 10:12 am, aaq via qubes-users wrote:
>
> > 6) Resizing a urxvt window in my debian unstable to a certain dimension
> > (or fullscreen hotkey) crashes the terminal. If I have another window
Den fredag den 12. januar 2018 kl. 10.45.02 UTC+1 skrev a...@it-minds.dk:
> Den mandag den 8. januar 2018 kl. 14.29.06 UTC+1 skrev Ahmed Al Aqtash:
> > Hello all!
> >
> >
> > I apologise for the vague subject, but I have been trying all kinds of
> > things, and I simply can't understand half of
Den mandag den 8. januar 2018 kl. 14.29.06 UTC+1 skrev Ahmed Al Aqtash:
> Hello all!
>
>
> I apologise for the vague subject, but I have been trying all kinds of
> things, and I simply can't understand half of the issues, and the other half
> I can't seem to find a solution to.
>
>
> First of
Den onsdag den 10. januar 2018 kl. 10.05.32 UTC+1 skrev Rune Philosof:
> On Saturday, June 25, 2016 at 7:49:39 PM UTC+2, cubit wrote:
> > To use the Windows Key, it is `Mod4`
> >
> >
> > "Mod4-c"
> > "Mod4-v"
>
> How did you figure that out?
> I haven't been able to find documentation with a lis
Den mandag den 8. januar 2018 kl. 14.52.43 UTC+1 skrev Tom Zander:
> On Monday, 8 January 2018 13:29:02 GMT 'Ahmed Al Aqtash' via qubes-users
> wrote:
> > * One I call 'trusted' which is based on debian sid (unstable) that I
> > install everything I use for daily usage (firefox, libreoffice, mpv
Den mandag den 8. januar 2018 kl. 14.29.06 UTC+1 skrev Ahmed Al Aqtash:
> Hello all!
>
>
> I apologise for the vague subject, but I have been trying all kinds of
> things, and I simply can't understand half of the issues, and the other half
> I can't seem to find a solution to.
>
>
> First of
> > * One I call 'trusted' which is based on debian sid (unstable) that I
> > install everything I use for daily usage (firefox, libreoffice, mpv,
> > emacs, other open source tools). Primarily AppVM's will be based out of
> > this template.
> >
> > * One I call 'untrusted' that is going to be a
> The same functionality is present in Qubes4, just not via a GUI.
>
> open a terminal in dom0 (adminvm) and type;
>
> qvm-prefs -s YOURVMNAME netvm sys-firewall
>
> When you are done downloading consider unsetting the netvm with;
> qvm-prefs -s YOURVMNAME netvm ""
I thought so, I just can't se
40 matches
Mail list logo